Labels
Prioritized labels 9
Drag to reorder prioritized labels and change their relative priority.
-
frontendGitLab.orgIssues for the Frontend team. Covers everything related to the way GitLab behaves (and, to an extent, looks) inside your browser.
-
golangGitLab.orgIssues for Ruby teams that require some knowledge of Go, because they may require changes in Gitaly, Workhorse, etc
-
workflowready for developmentGitLab.orgIssue has been broken down and prioritized by PM for development https://handbook.gitlab.com/handbook/product-development-flow/#description-4
-
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
-
workflowverificationGitLab.orgEverything has been merged, waiting for verification after a deploy https://handbook.gitlab.com/handbook/product-development-flow/#description-5
Labels 3,527
-
project import [DEPRECATED]GitLab.orgIssues related to importing repositories from GitLab or external systems
-
prototypebetaGitLab.orgUsed to label features that are in Beta https://docs.gitlab.com/ee/policy/alpha-beta-support.html#beta
-
prototypeexperimentGitLab.orgUsed to label features that are Experimental (https://docs.gitlab.com/ee/policy/alpha-beta-support.html#experiment)
-
prototypegeneral_availabilityGitLab.orgUsed to label features that are moving to General Availability https://docs.gitlab.com/ee/policy/alpha-beta-support.html#generally-available-ga
-
provision failureGitLab.orgIntroduced as part of the incident issue creation for a failed provision (https://gitlab.com/gitlab-org/customers-gitlab-com/-/issues/5254).
-
publishedGitLab.orgThis merge request will be published in a self-managed GitLab release. This label is added using the Release Tools project, and should not be manually added to merge requests.
-
purchase directionadminGitLab.orgnot aligned to strategy but business necessary: https://about.gitlab.com/direction/fulfillment/purchase/#vision-mission-strategy-and-outcomes
-
purchase directionin reviewGitLab.orgDetermining what strategy this body of work falls into: https://about.gitlab.com/direction/fulfillment/purchase/#vision-mission-strategy-and-outcomes
-
purchase maintenancebillable membersGitLab.orgMaintenance issues for group::purchase in the Billable Members category