Labels

A deliverable is a tangible or intangible output produced as a result of a project that is intended to be delivered to a client, either internal or external to the organization. It can be a report, a document, a piece of software, a service, or any other building block that contributes to the overall project.

An epic can represent a significant feature, a comprehensive project phase, or any large-scale initiative that requires multiple steps or components to complete. Epics are useful for tracking the progress of major objectives over time, providing a high-level overview of the work being done and how individual issues contribute to broader goals. They help in organizing and planning work by breaking down large projects into manageable units, making it easier for teams to prioritize tasks and monitor overall progress. Epics also facilitate communication among team members by centralizing related work and discussions in one place.

Tasks reviewed by QA team and still require a fix

Label for tickets for which the first planned deadline was not reached. These tickets must be documented, what was the reason for the unforeseen event.

You will use these label on an epic board to facilitate feature-level release prioritization. Items marked with priority later must be reviewed after each iteration to complete information and assign proper due dates

You will use these label on an epic board to facilitate feature-level release prioritization. Items marked with priority next must be attended as soon as there are not any priority now items.

You will use these label on an epic board to facilitate feature-level release prioritization. Items marked with priority now must be attended as soon as possible

Label to identify the backend team responsible for the ticket in Sprint mixes.

Label to identify the devops team responsible for the ticket in Sprint mixes.

Label to identify the frontend team responsible for the ticket in Sprint mixes.

This label is used to mark issues or merge requests that represent a flaw or problem in the application. It indicates something is not working as expected, potentially causing disruptions or unintended behavior. Ideal for prioritizing fixes and tracking bugs through to resolution.

Assigned to issues or merge requests that introduce new functionality or enhancements to the existing application. This label helps in categorizing work that adds value or improves the user experience, making it easier to manage feature development.

Utilized for issues or merge requests that capture user-centric needs or improvements, often described from the perspective of an end-user. Stories help in understanding the context and value of a feature, focusing on user satisfaction and requirements.

Applied to issues or merge requests that involve general tasks, which may include refactoring, documentation, setup, and other non-user-facing activities. This label is crucial for tracking work that supports the development process but doesn't directly contribute to new features or bug fixes.

Signifies that work on the issue or merge request is currently underway. It's used to track items that are actively being worked on by developers, highlighting ongoing efforts and work allocation.

Marks the stage where the implemented solution is undergoing review by peers, leads, or automated tests. It is a critical phase for ensuring quality and adherence to project standards before merging or moving forward.

Indicates that the issue or merge request has been fully planned and is now ready for developers to start working on. It means all prerequisites, such as designs and specifications, have been completed and approved.

Used when work on an issue or merge request is temporarily paused. This could be due to dependencies, prioritization changes, or awaiting further information. It helps in managing and revisiting paused tasks effectively.