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
- Work items
- Merge requests
-
directionGitLab.orgIssues for important features that are on our roadmap: https://about.gitlab.com/direction/
Labels 4,165
-
support_backlogtodoGitLab.orgNeeds to be assessed for ~"Customer Interest" in context of "Healthy Backlog" &18639
-
supports epic assignees workflowsGitLab.orgThis is a temporary label tagged to work items which are need to fully support epic assignees workflows.
-
suppress-contributor-linksGitLab.orgThe label will prevent links being added to manage the issue via the contributor platform. See https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links
-
team activitiesGitLab.orgItems that are related to CI/CD UX team activities and need attention / feedback from the members.
-
teamFrameworksGitLab.orgScalability:Frameworks team https://about.gitlab.com/handbook/engineering/infrastructure/team/scalability
-
teamsGitLab.orgIssues and Epics relating to teams, which is a feature owned by the Manage:Spaces group
-
technical debtGitLab.orgWork items to clean up or improve existing code that needs attention. This includes follow-ups from code reviews and areas we've identified that could have better implementations. See gitlab-com/content-sites/handbook!10641.