Group covering Navigations, Settings, and Notifications.

Issues belonging to the Global Search group of the Core Platform stage of the DevOps lifecycle.

Issues belonging to the Provision group of the Fulfillment stage of the DevOps lifecycle. See https://about.gitlab.com/handbook/product/categories/#provision-group

Issues related to search using the search field in the top navigation bar

[DEPRECATED] Adoption was a group in the Fulfillment section. See https://about.gitlab.com/handbook/product/categories/#fulfillment-section

Model Experiments allows Data Scientists to track candidates for their machine learning models

Issues and epics belonging to the Subscription Management group of the Fulfillment stage.

Issues belonging to the Authorization group of the Govern stage of the DevOps lifecycle, https://about.gitlab.com/handbook/product/categories/#authorization-group

label for the fulfillment subscription team

Issues belonging to the Observability group of the Analyze stage, for product category Error Tracking. See https://about.gitlab.com/handbook/product/categories/#observability-group

Issues related to the effort of having a Modular Monolith and #modular_monolith Slack channel discussions

Indicates that the structure.sql can be changed without introducing migrations

Code Search Category is part of Global Search that focuses on searching through Code Across Repositories

Changes to Architecture Evolution Blueprints described at https://about.gitlab.com/handbook/engineering/architecture/workflow/

Secure: Issues being worked on by the Secure Analyzer Frontend Team

SaaS services for the US Public Sector

Issue has gone through Quad Planning process (PM,Dev,UX,QE) and does not require any additional action

SaaS services for the US Public Sector

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

Issues related to Persistence (workspaces, caching). Does not include artifacts, which is its own label

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

Priority 1 for the assigned milestone.

This label is for things related to the Risk and Field Security team

Priority 2 for the assigned milestone.

Priority 3 for the assigned milestone.

Priority 4 for the assigned milestone.

Issues scheduled for the current milestone.

Issues related to CI rules or linting

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 current milestone's top product priorities for the Pipeline Execution group in the Verify stage

Issues related to next milestone's top product priorities for the Pipeline Execution group in the Verify stage

Issues related to future milestone's top product priorities for the Pipeline Execution group in the Verify stage

Issues or MRs that introduce user-facing changes or impact the user experience. Applying this label to issues will signal a need for a designer.