Labels
Prioritized labels 7
Drag to reorder prioritized labels and change their relative priority.
-
securityGitLab.orgIssues related to the security of GitLab or its dependencies. Please report vulnerabilities responsibly per https://about.gitlab.com/security/disclosure/
-
customerGitLab.orgIssues that were reported by Enterprise Edition subscribers. This label should be accompanied by either the 'bug' or 'feature proposal' label
-
customer+GitLab.orgFeatures and bugs reported by large enterprise customers. This label is in use by the product org, please post in #product Slack channel if you have questions.
-
typebugGitLab.orgIssues that report undesirable or incorrect behavior. See https://handbook.gitlab.com/handbook/product/groups/product-analysis/engineering/metrics/#work-type-classification
- Lock on merge
- Issues
- Merge requests
-
directionGitLab.orgIssues for important features that are on our roadmap: https://about.gitlab.com/direction/
Labels 3,891
-
workflowplanning breakdownGitLab.orgIssues that need estimation, and possibly breaking down into further chunks to enable effective iteration https://handbook.gitlab.com/handbook/product-development/how-we-work/product-development-flow/#build-phase-1-plan
-
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://handbook.gitlab.com/handbook/product-development/how-we-work/product-development-flow/#validation-phase-2-problem-validation
-
workflowready for designGitLab.org(optional) PM and Design prioritized design backlog of the next issues to be done https://handbook.gitlab.com/handbook/product-development/how-we-work/product-development-flow/#validation-phase-3-design
-
workflowready for developmentGitLab.orgIssue has been broken down and prioritized by PM for development https://handbook.gitlab.com/handbook/product-development/how-we-work/product-development-flow/#build-phase-1-plan
-
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" https://handbook.gitlab.com/handbook/product-development/how-we-work/product-development-flow/#build-phase-1-plan
-
workflowschedulingGitLab.orgIssues that are ready for development but are not yet active (or have an associated release) https://handbook.gitlab.com/handbook/product-development/how-we-work/product-development-flow/#build-phase-1-plan
-
workflowsolution validationGitLab.orgWorkflow label for validating that the proposed solution meets user needs https://handbook.gitlab.com/handbook/product-development/how-we-work/product-development-flow/#validation-phase-4-solution-validation
-
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://handbook.gitlab.com/handbook/product-development/how-we-work/product-development-flow/#validation-phase-1-validation-backlog
-
workflowverificationGitLab.orgEverything has been merged, waiting for verification after a deploy https://handbook.gitlab.com/handbook/product-development/how-we-work/product-development-flow/#build-phase-2-develop--test
-
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