Prioritized labels 7
Drag to reorder prioritized labels and change their relative priority.
security
GitLab.org
Issues related to the security of GitLab or its dependencies. Please report vulnerabilities responsibly per https://about.gitlab.com/security/disclosure/
customer
GitLab.org
Issues that were reported by Enterprise Edition subscribers. This label should be accompanied by either the 'bug' or 'feature proposal' label
customer+
GitLab.org
Features and bugs reported by large enterprise customers. This label is in use by the product org, please post in #product Slack channel if you have questions.
typebug
GitLab.org
Issues that report undesirable or incorrect behavior. See https://about.gitlab.com/handbook/engineering/metrics/#work-type-classification
- Lock on merge
- Issues
- Merge requests
direction
GitLab.org
Issues for important features that are on our roadmap: https://about.gitlab.com/direction/
Labels 2,993
prodops:feedbackloops
GitLab.org
Applies to to Product Operations work focusing on building qualitative & quantitative feedback loops.
prodops:knowledge
GitLab.org
Applies to to Product Operations work focusing on scaling product knowledge.
prodops:outcomes
GitLab.org
Applies to to Product Operations work supporting operationalizing outcome driven products.
prodops:related
GitLab.org
This 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:release
GitLab.org
Applies to epics, issues or MRs that should be highlighted on a Product Operations release page.
product category
GitLab.org
product discovery [DEPRECATED]
GitLab.org
A 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 intelligence
GitLab.org
Assigned to MRs when danger bot detects changes to tracking/metrics related files to kick off approval process.
product intelligenceapproved
GitLab.org
Product Analytics(Telemetry) changes are reviewed and ready to be approved by Product Analytics(Telemetry) Reviewer/Maintainer
product intelligencereview pending
GitLab.org
Product Analytics(Telemetry) changes require a review from Product Analytics(Telemetry) Reviewer/Maintainer
product planningneeds review
GitLab.org
This epic or issue needs product review to validate need and/or schedule.
product planningparked
GitLab.org
In 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 planningscoping
GitLab.org
This 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 work
GitLab.org
Issues for the Product team. Covers issues that still need to be worked out before UX / Dev can work on it
production request
GitLab.org
Changes to the GitLab application requested by the GitLab Infrastructure Team that would improve the administration and management of GitLab.com