Labels

Label to communicate potential security operational risks to the Security Risk Team

Additional information is required to support the Security Risk Team's StORM Risk Assessment

A Risk Owner needs to be identified

The Security Risk Team performed a StORM Risk Assessment and determined that the potential risk identified is out of scope for the StORM program because it is not considered an operational security risk.

Label used to note the Security Risk Team is currently assessing a potential risk

Issues that were once scheduled but have been demoted. This is intended to highlight issues that may be in a more refined state or ready to pick up again.

Issues that are a stretch goal for delivering in the current milestone. If these issues are not done in the current release, they will strongly be considered for the next release.

Used by contributors that are currently students at an educational institution

We allow development to fix small problems they see in the code base without an issue that are incremental improvements. Tag issues/merge requests for work in this area.

Issues and MRs that improve GitLab Support Team's efficiency (same as for gitlab-com). This label gets added typically when an issue comes up multiple times. For Fulfillment, use scoped labels.

Used by GitLab Support to indicate an issue or epic of interest to them except in Fulfillment (use scoped labels)

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/