Labels can be applied to issues, merge requests, and epics. Group labels are available for any project within the group.
Labels
-
workflowissue reviewedGitLab.orgProduct managers use this label when they've completed an issue peer review.
-
workflowneeds issue reviewGitLab.orgProduct managers use this label when their issue needs to be reviewed.
-
workflowplanning breakdownGitLab.orgIssues that need estimation, and possibly breaking down into further chunks to enable effective iteration. https://about.gitlab.com/handbook/product-development-flow/
-
workflowpost-deploy-db-productionGitLab.orgPost-migrations on the merge request have been executed in GitLab.com
-
workflowpost-deploy-db-stagingGitLab.orgPost-migrations on the merge request have been executed in staging.gitlab.com.
-
workflowproblem validationGitLab.orgWorkflow label for validating if the problem is customer relevant. https://about.gitlab.com/handbook/product-development-flow/#workflow-summary
-
workflowready for designGitLab.org(optional) PM and Design prioritized design backlog of the next issues to be done
-
workflowready for reviewGitLab.orgMerge 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.
-
workflowrefinementGitLab.orgIssues that need further input from team members in order for it to be "workflow::ready for development"
-
workflowschedulingGitLab.orgIssues that are ready for development but are not yet active (or have an associated release). https://about.gitlab.com/handbook/product-development-flow/
-
workflowsolution validationGitLab.orgWorkflow label for validating that the proposed solution meets user needs. https://about.gitlab.com/handbook/product-development-flow/
-
workflowstartGitLab.orgThe 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.
-
workflowvalidation backlogGitLab.orgIssues 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
-
workflowverificationGitLab.orgEverything has been merged, waiting for verification after a deploy.
-
workflowversion promotedGitLab.orgSuccessfully 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
Prioritized