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,476
-
Container Registry Self-Managed Rollout::BlocksExperimentalGitLab.org / container-registry
-
See &5521 for details
-
See &5521 for details
-
See &5521 for details
-
See &5521 for details
-
Contribute2020GitLab.orgIssues related to planning Contribute 2020 https://about.gitlab.com/events/gitlab-contribute/
-
Contribute2020-challengeGitLab.orgRelated to the Contribute Challenge of April 2020: Beautifying the Docs
-
Contribute2020-challenge-followupGitLab.orgFuture proposals and work resulting from the Contribute Challenge in April 2020
-
Contributor SuccessGitLab.orgIssues of interest to the Contributor Success team. More at https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/
-
Core Platform:TrackingGitLab.orgUsed by the Core Platform sub-department to track spike, testing, operational efforts that do not result in product MRs
-
Create [DEPRECATED]GitLab.orgPlease use the devops::create label instead of this deprecated label. It is kept for historical issues.