Labels
Prioritized labels 25
Drag to reorder prioritized labels and change their relative priority.
-
Category:ServerlessGitLab.orgAll issues and MRs related to the Serverless category within devops::configure. https://about.gitlab.com/direction/configure/serverless/
-
dockerfileGitLab.org / GitLab Docs DEPRECATEDRelated to the dockerfiles present in the gitlab-docs project
-
Category:Chaos EngineeringGitLab.orgIssues related to chaos engineering (part of ~devops:configure stage)
-
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)
-
Category:Infrastructure as CodeGitLab.orgAll issues and MRs related to the Infrastructure as Code category within devops::configure. https://about.gitlab.com/direction/configure
-
[deprecated] Accepting merge requestsGitLab.org[deprecated] Please use "Seeking community contributions" instead. gitlab-org/developer-relations/contributor-success/team-task#77
-
Category:Cluster MonitoringGitLab.orgIssues belonging to the Monitor stage Health group for product category Cluster Monitoring
-
Category:Auto DevOpsGitLab.orgIssues for Auto DevOps, part of the Configure stage of the DevOps lifecycle
-
Category:Code QualityGitLab.orgAll issues and MRs related to the Code Quality category. See https://about.gitlab.com/direction/secure/static-analysis/code-quality/
-
Category:Container RegistryGitLab.orgCategory label - Features that apply to management container registries
-
groupconfigure [DEPRECATED]GitLab.org[DEPRECATED] should use group::environments. Issues belonging to the Configure group of the Configure stage of the DevOps lifecycle. See https://about.gitlab.com/handbook/product/categories/#configure-group
-
Category:Continuous IntegrationGitLab.orgAll issues and MRs related to the continuous integration category within devops:verify https://about.gitlab.com/direction/verify/continuous_integration
-
infrastructure configurationGitLab.orgIssues for Infrastructure Configuration, part of the Configure stage of the DevOps lifecycle
-
Category:Cluster Cost OptimizationGitLab.orgIssues related to the "cluster cost optimization" category of the configure stage. See &503
-
Category:Cloud Native InstallationGitLab.org
-
development guidelinesGitLab.orgChanges or updates to the development guidelines in the /development directory in the GitLab documentation. (Info: https://docs.gitlab.com/ee/development/)
-
groupsource codeGitLab.orgIssues belonging to the Source Code group of the Create stage of the DevOps lifecycle. See https://about.gitlab.com/handbook/product/categories/#source-code-group
-
grouprunner coreGitLab.orgIssues belonging to the Runner group of the Verify stage of the DevOps lifecycle.
-
Category:Kubernetes ManagementGitLab.orgRelating the `Kubernetes Management` category within the configure stage
Labels 3,627
-
Design Priority1GitLab.orgUse this label when you want to mark the priority of a design issue as the top priority (i.e. do this first as the top priority 1) where you're expecting to deliver it at a 100% by the defined due date.
-
Design Priority2GitLab.orgUse this label when you want to mark the priority of a design issue as the second most important priority (i.e. do this second as the next priority 2) where you're expecting to deliver it at 80% by the defined due date.
-
Design Priority3GitLab.orgUse this label when you want to mark the priority of a design issue as the third-highest priority (i.e. do this third as the medium priority 3) where you're expecting to deliver it at 60% by the defined due date.
-
Design Priority4GitLab.orgUse this label when you want to mark the priority of a design issue as the fourth-highest priority (i.e. do this later as a lower priority 4) where you're expecting to deliver it at 40% by the defined due date.
-
Design Priority5GitLab.orgUse this label when you want to mark the priority of a design issue as the fifth-highest priority (i.e. do this later as a lower priority 5) where you're expecting to deliver it at 20% by the defined due date.
-
Design Priority6GitLab.orgUse this label when you want to mark the priority of a design issue as the sixth-highest priority (i.e. do this last as the least priority 6) where you're expecting to deliver it at 10% by the defined due date.
-
DevOps ScoreGitLab.orgPreviously "convdev". Issues related to GitLab's initiative to surface relevant data analytics to user in the area of Contribution Analytics and Conversational Development
-
DevSecOps AdoptionGitLab.orgRelated to one or more DevSecOps Adoption product themes. See https://internal.gitlab.com/handbook/product/devsecops-adoption/priorities/ (team members only) Questions about this label? Ask Sec PM team. Label creator: @connorgilbert
-
Distribution KR1GitLab.orgDistribution key result 1, usually combines with objective and quarterly label.
-
Distribution KR2GitLab.orgDistribution key result 2, usually combines with objective and quarterly label.
-
Distribution KR3GitLab.orgDistribution key result 3, usually combines with objective and quarterly label.
-
Distribution KR4GitLab.orgDistribution key result 4, usually combines with objective and quarterly label.