An issue which has been validated and ready for planning/design/development. This label is being used as part of an experiment and should not be manually added/removed. See gitlab-org/developer-relations/contributor-success/team-task#382

Outlier that relates to a single distribution, platform, or architecture (eg Debian/AWS/ARM/)

Issues migrated from Platform label to Create label Ref: gitlab-org/quality/triage-ops#59

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.