Labels

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

The MRs created by DeleteOldFeatureFlags keep.

Issues belonging to the Container Registry group of the Package stage of the DevOps lifecycle. See https://about.gitlab.com/handbook/product/categories/#container-registry-group

Label for the Organizations group within Tenant Scale

Quick win issues that are ideal for first-time community contributors to work on

Category for issues related to email notifications and to-dos

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

Issue with low technical complexity. Complexity does not describe the time it will likely require to address the issue, but rather the familiarity required to address it. This label is only intended as a guideline to hint to individuals how involved the issue will likely be.

Issues that are ready for development and should be worked on next.

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

Issue with medium technical complexity. Complexity does not describe the time it will likely require to address the issue, but rather the familiarity required to address it. This label is only intended as a guideline to hint to individuals how involved the issue will likely be.

Issues that are actively being worked on by a developer https://handbook.gitlab.com/handbook/product-development-flow/#description-5

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

Issue with high technical complexity. Complexity does not describe the time it will likely require to address the issue, but rather the familiarity required to address it. This label is only intended as a guideline to hint to individuals how involved the issue will likely be.

Issues that are blocked until another issue has been completed https://handbook.gitlab.com/handbook/product-development-flow/#description-5

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

Applied after all MRs have merged and the issue has been verified if necessary https://handbook.gitlab.com/handbook/product-development-flow/#build-phase-3-launch

Issues that are undergoing code review by the development team and/or undergoing design review by the UX team https://handbook.gitlab.com/handbook/product-development-flow/#description-5

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

Issues that need further input from team members in order for it to be "workflow::ready for development" https://handbook.gitlab.com/handbook/product-development-flow/#build-phase-1-plan

Merge request has been deployed to staging.gitlab.com.

Merge requests which are ready to be reviewed and can be reviewed by any team-member with sufficient knowledge in the given area. For reviewing the merge request just assign to yourself and remove this label.

Workflow label for validating that the proposed solution meets user needs https://handbook.gitlab.com/handbook/product-development-flow/#validation-phase-4-solution-validation

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

Enabled through a separate feature flag rollout issue. https://handbook.gitlab.com/handbook/engineering/development/ops/verify/pipeline-execution/#workflow

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

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 or MRs that introduce user-facing changes or impact the user experience. Applying this label to issues will signal a need for a designer.