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,479
-
Deferred UXGitLab.orgA follow-up issue for when we choose to deviate from the MVC, during implementation, in a way that harms the user experience. https://about.gitlab.com/handbook/engineering/workflow/#deferred-ux
-
Description templates (.gitlab/*)GitLab.orgCreate and update issue and MR templates in `.gitlab/*` (dev guidelines)
-
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