Labels

Feature proposals deemed popular by our issue triage policies (https://gitlab.com/gitlab-org/triage) will have this label applied

for issues relating to the customer portal integrating with another ent app

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/