Labels can be applied to issues, merge requests, and epics. Group labels are available for any project within the group.
Labels
-
Web IDE issues which HAVE been prioritized into the current iteration or a future iteration.
-
Web IDE issues which have NOT yet been prioritized into the current iteration or a future iteration.
-
This is a security issue that is ready to be deployed but awaiting a security release
-
Issues that are blocked until another issue has been completed
-
Applied after all MRs have merged and the issue has been verified if necessary
-
Ideate solutions to well-defined customer problems https://about.gitlab.com/handbook/product-development-flow/#validation-phase-3-design
-
Was not advanced beyond the current version (experimental or beta). See https://docs.gitlab.com/ee/policy/alpha-beta-support.html
-
Issues for features that are being enabled through a separate feature flag rollout issue
-
Issues that are undergoing code review by the development team and/or undergoing design review by the UX team
-
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 need estimation, and possibly breaking down into further chunks to enable effective iteration. https://about.gitlab.com/handbook/product-development-flow/
-
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://about.gitlab.com/handbook/product-development-flow/#workflow-summary
-
(optional) PM and Design prioritized design backlog of the next issues to be done
Prioritized