Labels can be applied to issues, merge requests, and epics. Group labels are available for any project within the group.
Labels
-
Issues that are ready for development but are not yet active (or have an associated release). https://about.gitlab.com/handbook/product-development-flow/
-
Workflow label for validating that the proposed solution meets user needs. https://about.gitlab.com/handbook/product-development-flow/
-
Merge request is deployed to the staging canary environment.
-
Merge request is deployed to the staging ref environment.
-
The entry point for workflow scoped labels. From here, Issues will either move through the validation workflow, go directly to planning and scheduling, or in certain cases, go directly to the development steps.
-
Issues in a backlog of potential validation opportunities. This label is part of the product development flow https://about.gitlab.com/handbook/product-development-flow/#workflow-summary
-
Everything has been merged, waiting for verification after a deploy.
-
Successfully completed the current version (experimental or beta) and promoted to the next version (beta or GA). See https://docs.gitlab.com/ee/policy/alpha-beta-support.html
-
Remote Development Workspaces issues which have already been closed in previous iterations
-
Remote Development Workspaces issues that are being ignored from the current rd-workflow process and automation.
-
Remote Development Workspaces issues which HAVE been prioritized into the current iteration or a future iteration.
-
Remote Development Workspaces issues which have NOT yet been prioritized into the current iteration or a future iteration.
Prioritized