Labels

Label added by triage tools to mark interesting feature proposals for consideration

Issues that we anticipate yielding higher predictability (vs. velocity).

We will address this as soon as possible regardless of limit on our team capacity. See https://handbook.gitlab.com/handbook/engineering/infrastructure/engineering-productivity/issue-triage/#priority

We will address this soon and will provide capacity from our team for it in the next few releases. See https://handbook.gitlab.com/handbook/engineering/infrastructure/engineering-productivity/issue-triage/#priority

We want to address this but may have other higher priority items. See https://handbook.gitlab.com/handbook/engineering/infrastructure/engineering-productivity/issue-triage/#priority

We don't have visibility when this will be addressed. See https://handbook.gitlab.com/handbook/engineering/infrastructure/engineering-productivity/issue-triage/#priority

Issues related to general work process

Applies to epics, issues or MRs that should be highlighted on a Product Operations direction page.

Applies to to Product Operations work focusing on building qualitative & quantitative feedback loops.

Applies to to Product Operations work focusing on scaling product knowledge.

Applies to to Product Operations work supporting operationalizing outcome driven products.

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.

Applies to epics, issues or MRs that should be highlighted on a Product Operations release page.

Related to https://about.gitlab.com/handbook/product/categories/

applies to work related to the product development flow

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.

applies to work related to the product handbook

Assigned to MRs when danger bot detects changes to tracking/metrics related files to kick off approval process.

Product Analytics(Telemetry) changes are reviewed and ready to be approved by Product Analytics(Telemetry) Reviewer/Maintainer

Product Analytics(Telemetry) changes require a review from Product Analytics(Telemetry) Reviewer/Maintainer