Labels
Labels can be applied to issues, merge requests, and epics. Group labels are available for any project within the group.
Labels 4,179
-
Product managers use this label when they've completed an issue peer review.
-
Product managers use this label when their issue needs to be reviewed.
-
Issues that are ready for development and should be worked on next.
-
Issues that need estimation, and possibly breaking down into further chunks to enable effective iteration https://handbook.gitlab.com/handbook/product-development/how-we-work/product-development-flow/#build-phase-1-plan
-
Post-migrations on the merge request have been executed in GitLab.com
-
Post-migrations on the merge request have been executed in staging.gitlab.com.
-
Workflow label for validating if the problem is customer relevant. https://handbook.gitlab.com/handbook/product-development/how-we-work/product-development-flow/#validation-phase-2-problem-validation
-
(optional) PM and Design prioritized design backlog of the next issues to be done https://handbook.gitlab.com/handbook/product-development/how-we-work/product-development-flow/#validation-phase-3-design
-
Issue has been broken down and prioritized by PM for development https://handbook.gitlab.com/handbook/product-development/how-we-work/product-development-flow/#build-phase-1-plan
-
Merge requests which are ready to be reviewed and can be reviewed by any team-member with sufficient knowledge in the given area. For reviewing the merge request just assign to yourself and remove this label.
-
Issues that need further input from team members in order for it to be "workflow::ready for development" https://handbook.gitlab.com/handbook/product-development/how-we-work/product-development-flow/#build-phase-1-plan
-
Issues that are ready for development but are not yet active (or have an associated release) https://handbook.gitlab.com/handbook/product-development/how-we-work/product-development-flow/#build-phase-1-plan
-
Workflow label for validating that the proposed solution meets user needs https://handbook.gitlab.com/handbook/product-development/how-we-work/product-development-flow/#validation-phase-4-solution-validation
-
Merge request has been deployed to staging.gitlab.com.
-
Merge request is deployed to the staging canary environment.
-
Merge request is deployed to the staging ref environment.