[DRAFT] Vega dev-testable

Using the JIRA label: dev-testable

Purpose

The dev-testable label is used to identify tasks that do not require standard QA/PO testing and whose testing can or should be performed by developers.
This helps optimize the testing process and avoid transferring tasks to the QA/PO queue, where they cannot be adequately tested without specialized tools, an environment, a deep understanding of the implementation, etc.

Scope

This label should be used in the following cases:
Infrastructure/CI/CD Changes: Tasks related to changing configuration files, updating libraries, etc.
Code Refactoring: Internal changes aimed at improving readability, performance, or architecture that do not change the external behavior of the application (provided that test coverage guarantees the absence of regression).
Specific Technical Tasks: Tasks whose testing requires access to internal systems, specific logs, or tools unavailable to the QA/PO team. Technical Tasks: Spikes, Releases, etc.

Usage Guidelines

When to Use the Label:

Only with the approval of the Dev BE/FE Lead/Tech Lead. Use of this label must be justified and approved.
The developer using this label is solely responsible for testing the issue and ensuring there are no regressions.
The developer must provide a detailed description of the tests performed in the comments to the JIRA issue before closing it (if applicable).

When NOT to Use the Label:

Never use for issues related to the business logic of the application.
Never use for bug fixes (such bugs require mandatory independent testing).

Issue Workflow

When the dev-testable label is used, the standard transition of the issue from the "In Testing" to "In Review" status is skipped. Instead, the following path is used:
Open -> In Progress -> In Code Review (if applicable) -> Done
Required steps before closing (status "Done"):
The developer writes a comment in JIRA describing how they reviewed their work (if applicable) and waits for the next working build to ensure the build was problem-free.
The issue is closed by the Dev BE/FE Lead/Tech Lead.

Accountability

Using this label is a tool for trust and accountability. Overuse or omission of testing when using this label will result in a review of the process and possibly its discontinuation.