Labels

https://gitlab.com/gitlab-com/govern-compartment/-/issues

Ops Sub-Department within Development https://about.gitlab.com/handbook/engineering/development/ops/

Secure sub-department teams

Use this label for issues related to the transition from Support-Resources to the Cloud Sandbox

For MRs that improve GitLab Support Team's efficiency (same as for gitlab-org)

Indicates Support Readiness is not needed on this issue at the current time

For issues that require attention from the Support team before they can process tickets

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://about.gitlab.com/handbook/support/license-and-renewals/workflows/managing_product_issues.html

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