You need to sign in or sign up before continuing.
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,592
-
workflowin devGitLab.orgIssues that are actively being worked on by a developer https://handbook.gitlab.com/handbook/product-development-flow/#description-5
-
workflowin reviewGitLab.orgIssues 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
-
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://handbook.gitlab.com/handbook/product-development-flow/#description-4
-
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-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-flow/#outcomes-and-activities-2
-
workflowready for developmentGitLab.orgIssue has been broken down and prioritized by PM for development https://handbook.gitlab.com/handbook/product-development-flow/#description-4
-
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-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-flow/#description-4
-
workflowsolution validationGitLab.orgWorkflow label for validating that the proposed solution meets user needs https://handbook.gitlab.com/handbook/product-development-flow/#validation-phase-4-solution-validation