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,478
-
Data WarehouseImpact CheckGitLab.orgIndicates that Data Team should perform a impact check on the MR
-
Data team reviewGitLab.orgProvide the data team with awareness of an issue that may affect data (reporting, compliance, process)
-
DataSec501(c)(13) InvestigationGitLab.orgIndicates that the issue is related to an ongoing DataSec investigation of legacy code and infrastructure.
-
DataSecConsultGitLab.orgThis label indicates DataSec is doing some kind of miscellaneous work with this issue (i.e., consultative work at the request of another team that isn't spawning its own issue in our board).
-
Database EngineeringGitLab.orgPertaining database engineering concepts, patterns, improvements, etc.