Tier 4 pipelines are not yet defined. See gitlab-org/quality/engineering-productivity&58 for more info.

Tier 3 pipelines are run when a merge request has all the approvals it needs. See gitlab-org/quality/engineering-productivity&58 for more info.

Tier 2 pipelines are run when a merge request has at at least one approval, but still requires more approvals. See gitlab-org/quality/engineering-productivity&58 for more info.

Tier 1 pipelines are run when a merge request has no approvals. See gitlab-org/quality/engineering-productivity&58 for more info.

Issues related to the Autonomous Agents directive for the GitLab. See https://docs.google.com/document/d/15N9G3UWoB_u8KOErdk_aGk5IdBoxEFBWMSgg9FvwVXo/edit#heading=h.j3rcm4sf2nc9

Indicates the work is done, or the rotation has finished.

Indicates the issue is actively being worked on, or the rotation is in progress.

Indicates that work has been triaged, scoped, and is ready to be worked on in the assigned milestone.

Needs Refinement - The issue is overly complex and needs to be promoted to an Epic or broken down into smaller issues https://handbook.gitlab.com/handbook/security/product-security/application-security/metrics/capacity/#table-1

XLarge - Very complex and requires a major portion of the milestone to resolve https://handbook.gitlab.com/handbook/security/product-security/application-security/metrics/capacity/#table-1

Large - Significant investigation and collaboration needed https://handbook.gitlab.com/handbook/security/product-security/application-security/metrics/capacity/#table-1

Medium - Some investigation and/or collaboration needed https://handbook.gitlab.com/handbook/security/product-security/application-security/metrics/capacity/#table-1

Small - Straight forward change, minimal investigation https://handbook.gitlab.com/handbook/security/product-security/application-security/metrics/capacity/#table-1

Trivial - Very little effort required https://handbook.gitlab.com/handbook/security/product-security/application-security/metrics/capacity/#table-1

Related to the launch of the Duo Enterprise paid add-on for customers.

To classify GitLab Duo Code Suggestions into the specific sub-type we are using. Often used to distinguish a feature from with "code completion"

To classify GitLab Duo Code Suggestions into the specific sub-type we are using. Often used to distinguish a feature from with "code generation"

Issues for the Package stage of the DevOps lifecycle (e.g. package registry, container registry)