Labels
Labels can be applied to issues, merge requests, and epics. Group labels are available for any project within the group.
Labels 3,505
-
Issue is appropriately scoped, estimated, and enqueued for work
-
Verify is a state after in-progress, before closed to make sure the work is done.
-
Indicates the issue has voluntary been put on hold because work is being done on higher priority items
-
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 https://handbook.gitlab.com/handbook/product-development-flow/#description-5
-
Applied after all MRs have merged and the issue has been verified if necessary https://handbook.gitlab.com/handbook/product-development-flow/#build-phase-3-launch
-
Ideate solutions to well-defined customer problems https://handbook.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
-
Enabled through a separate feature flag rollout issue. https://handbook.gitlab.com/handbook/engineering/development/ops/verify/pipeline-execution/#workflow
-
Issues that are actively being worked on by a developer https://handbook.gitlab.com/handbook/product-development-flow/#description-5
-
Issues that are undergoing code review by the development team and/or undergoing design review by the UX team https://handbook.gitlab.com/handbook/product-development-flow/#description-5
-
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-flow/#description-4
-
Post-migrations on the merge request have been executed in GitLab.com