Labels can be applied to issues, merge requests, and epics. Group labels are available for any project within the group.
Labels 2,884
-
Items related to epics migration that should be completed prior to internal rollout.
-
Items related to migrating issues to work items that should be completed prior to any internal rollout.
-
First priority after both issues and epic work items are GA. Does not block any rollout.
-
Non-blocking work items updates that are not top priority after migration.
-
Applied when closing incomplete work because it is decided that no more will be done on an issue or epic.
-
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.