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,452
-
Architecture Evolution BlueprintGitLab.orgChanges to Architecture Evolution Blueprints described at https://about.gitlab.com/handbook/engineering/architecture/workflow/
-
ArkoseGitLab.orgIssues relating to Arkose Labs, part of the Anti-Abuse group of the Anti-abuse Stage
-
Bad Suggested ReviewerGitLab.orgUse this label when the automatically Suggested Reviewer is not useful (Feature of AI-powered stage)
-
Beautifying our UIGitLab.orgThis label should only be used to track MRs created as part of the Beautifying our UI effort: https://about.gitlab.com/handbook/engineering/ux/product-design/#beautifying-our-ui
-
Breakdown SufficientGitLab.orgIssues in ~"workflow::planning breakdown" that have been fully broken down and estimated.