Labels

Indicates the priority of issues within the current iteration for the Runner team

Indicates the priority of issues within the current iteration for the Runner team

Priority items for Incubation Engineering

Label to signify that a bug issue has missed its targeted SLO (Service Level Objective). See https://docs.gitlab.com/ee/development/contributing/issue_workflow.html#priority-labels. Previously titled as missed-SLO

A label to denote the priority of issues related to the Security Operations T&S and SIRT OKR gitlab-com/gl-security/security-department-meta#1392

A label to denote the priority of issues related to the Security Operations T&S and SIRT OKR gitlab-com/gl-security/security-department-meta#1392

A label to denote the priority of issues related to the Security Operations T&S and SIRT OKR gitlab-com/gl-security/security-department-meta#1392

Used to denote an issue which will reduce ticket volume significantly. Typically added if repeatedly seen in customer tickets, and internally, by the Support team. EXCEPT IN L&R SUPPORT: For Fulfillment, apply this label to indicate an item of interest to L&R Support.

For Support<>Fulfillment: ONLY L&R Support DRIs should apply this label to an issue or epic to identify it as a top priority from Support. No more than 10 open issues and epics should have this priority at any time. See https://handbook.gitlab.com/handbook/support/license-and-renewals/workflows/managing_product_issues/

For Support<>Fulfillment: ONLY L&R Support DRIs should apply this label to an issue or epic to identify it as a top priority from Support. No more than 10 open issues and epics should have this priority at any time. See https://handbook.gitlab.com/handbook/support/license-and-renewals/workflows/managing_product_issues/

For Support<>Fulfillment: ONLY L&R Support DRIs should apply this label to an issue or epic to identify it as a lower priority item on Support's Issue List for Fulfillment. See https://handbook.gitlab.com/handbook/support/license-and-renewals/workflows/managing_product_issues/

For Support<>Fulfillment: ONLY L&R Support DRIs should apply this label to an issue or epic to identify it as a low priority item on Support's Issue List for Fulfillment. See https://handbook.gitlab.com/handbook/support/license-and-renewals/workflows/managing_product_issues/

For Support<>Fulfillment: Used when initially identifying a new or existing issue or epic as one to be included in Support's Issue List for Fulfillment. This identifies the item as needing to be categorized. See https://handbook.gitlab.com/handbook/support/license-and-renewals/workflows/managing_product_issues/

For Support<>Fulfillment: Use to indicate that the issue or epic on Support's Issue List for Fulfillment needs to be reviewed for possible reprioritization. Comment on the issue or epic outlining how you think it should be prioritized and your reasoning. See https://handbook.gitlab.com/handbook/support/license-and-renewals/workflows/managing_product_issues/

L&R Support uses this label as part of its monthly review of issues and epics to be prioritized (see https://gitlab.com/gitlab-com/support/licensing-subscription/fulfillment-requests/-/blob/main/.gitlab/issue_templates/monthly_prioritization.md)

For Support<>Fulfillment: ONLY L&R Support DRIs should apply this label to an issue or epic to identify it as a child of a prioritized epic on Support's Issue List for Fulfillment. See https://handbook.gitlab.com/handbook/support/license-and-renewals/workflows/managing_product_issues/

This label is used to assess risk on Duo Agent Platform tasks. UX involvement is highly recommended due to design complexity and high impact to users and/or the business.

This label is used to assess risk on Duo Agent Platform tasks. UX involvement is recommended due to moderate complexity and impact to users and/or the business.

This label is used to assess risk on Duo Agent Platform tasks. UX involvement is recommended, time permitting. This is for issues where a designers input will improve the experience or the clarity of the solution, but the risk of a negative impact to users and the business is low.

Large, strategic, rigorous projects that could benefit from a research specialist. Typically, foundational research, complex research questions, or high-priority problem validation.