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,525
-
prodops:relatedGitLab.orgThis label represents is used when an epic, issue or MR does not required direct contribution from Product Operations but required their awareness as it affects workflows, documentation, or is otherwise a dependency for Product Operations work.
-
prodops:releaseGitLab.orgApplies to epics, issues or MRs that should be highlighted on a Product Operations release page.
-
product categoryGitLab.org
-
product discovery [DEPRECATED]GitLab.orgA discovery issue intended for UX, PM, FE, and BE to discuss the problem and potential solutions. The final output for this issue could be a doc of requirements, a design artifact, or even a prototype. The solution will be developed in a subsequent milestone.
-
product intelligenceGitLab.orgAssigned to MRs when danger bot detects changes to tracking/metrics related files to kick off approval process.
-
product intelligenceapprovedGitLab.orgProduct Analytics(Telemetry) changes are reviewed and ready to be approved by Product Analytics(Telemetry) Reviewer/Maintainer
-
product intelligencereview pendingGitLab.orgProduct Analytics(Telemetry) changes require a review from Product Analytics(Telemetry) Reviewer/Maintainer
-
product planningneeds reviewGitLab.orgThis epic or issue needs product review to validate need and/or schedule.
-
product planningparkedGitLab.orgIn order to keep a manageable backlog of work we are actively focusing on, we apply the ~"product planning::parked" label to the epics/issues that we intend to check regularly, but do not plan any work on them currently.
-
product planningscopingGitLab.orgThis label signifies work that we are preparing as a candidate for an upcoming Quarterly plan. While in `scoping` we are ensuring the goal of the work, the usability expectations, what's included and not included are clear so that engineering can provide an estimate/feasibility of the work in the upcoming quarter.
-
product workGitLab.orgIssues for the Product team. Covers issues that still need to be worked out before UX / Dev can work on it
-
production requestGitLab.orgChanges to the GitLab application requested by the GitLab Infrastructure Team that would improve the administration and management of GitLab.com