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,843
-
developmentin-reviewGitLab.orgAn issue which has been validated, broken down, planned/designed, developed and is in review. This label is being used as part of an experiment and should not be manually added/removed. See gitlab-org/developer-relations/contributor-success/team-task#382
-
developmentto-doGitLab.orgAn issue which has been validated, broken down/planned/designed and is ready for development to begin. This label is being used as part of an experiment and should not be manually added/removed. See gitlab-org/developer-relations/contributor-success/team-task#382
-
developmentworkingGitLab.orgAn issue which has been validated, broken down/planned/designed and is in development. This label is being used as part of an experiment and should not be manually added/removed. See gitlab-org/developer-relations/contributor-success/team-task#382
-
devopsanti-abuseGitLab.orgIssues for the Anti-Abuse stage of the DevOps lifecycle (e.g. Anti-Abuse)
-
devopsapplication security testingGitLab.orghttps://handbook.gitlab.com/handbook/product/categories/#application-security-testing-stage (e.g. SAST, DAST, Secret Detection, Dependency Scanning, Vulnerability Database)
-
devopsconfigure [DEPRECATED]GitLab.org[DEPRECATED] should use devops::deploy now. Issues for the Configure stage of the DevOps lifecycle (e.g. Auto DevOps , Kubernetes Configuration, ChatOps, Serverless, PaaS)
-
devopscreateGitLab.orgIssues for the Create stage of the DevOps lifecycle (e.g. Source Code Management, Design Management, Web IDE, Code Review, Gitter)
-
devopsdata storesGitLab.orgIssues for the Data Stores stage of the DevOps lifecycle (Application Performance, Database, Global Search, Tenant Scale)
-
devopsdata_accessGitLab.orgLabel for the data access stage, hosting Gitaly, Git, Database Frameworks, Database Operations, and Durability groups.
-
devopsdeployGitLab.orgIssues for the Deploy stage of the DevOps lifecycle. https://about.gitlab.com/handbook/product/categories/#deploy-stage
-
devopsdeveloper experienceGitLab.orgIssues for the Developer Experience stage: https://handbook.gitlab.com/handbook/engineering/infrastructure-platforms/developer-experience
-
devopsfoundationsGitLab.orgIssues for the Foundations stage of the DevOps lifecycle (e.g. Import & Integrate, Personal Productivity, etc)
-
devopsfulfillmentGitLab.orgIssues for the Fulfillment stage of the DevOps lifecycle (e.g. Subscription App, License App)
-
devopsgitlab dedicatedGitLab.orgIssues for the GitLab Dedicated group of the SaaS Platforms section - https://about.gitlab.com/handbook/engineering/infrastructure/team/gitlab-dedicated/ Should make group::GitLab Dedicated obsolete.
-
devopsgitlab deliveryGitLab.orgIssues for the GitLab Delivery teams https://handbook.gitlab.com/handbook/engineering/infrastructure-platforms/gitlab-delivery/