Issues or MRs that are only for self-managed rather than jihulab.com (SaaS)

Blocker - applies to bugs and bug categories of availability, performance, security and ux. See https://about.gitlab.com/handbook/engineering/quality/issue-triage/#severity

Critical - applies to bugs and bug categories of availability, performance, security and ux. See https://about.gitlab.com/handbook/engineering/quality/issue-triage/#severity

Major - applies to bugs and bug categories of availability, performance, security and ux. See https://about.gitlab.com/handbook/engineering/quality/issue-triage/#severity

Low - applies to bugs and bug categories of availability, performance, security and ux. See https://about.gitlab.com/handbook/engineering/quality/issue-triage/#severity

Issue related to staging env

Issue related to staging-canary

Issues that report undesirable or incorrect behavior. See https://about.gitlab.com/handbook/engineering/metrics/#work-type-classification

Any issue/MR that contains work to support the implementation of a feature and/or results in an improvement in the user experience. Read more at https://about.gitlab.com/handbook/engineering/metrics/#work-type-classification

Refinements to an existing feature that are not user-facing and not related to `~"type::bug"` resolution. Read more at https://about.gitlab.com/handbook/engineering/metrics/#work-type-classification

Issues used to track a work in upstream repo

Usability improvement

Not a bug/feature that we should fix/implement. When you close an issue because it is actually not a bug or not a feature that we should implement, please ensure this label is added to the issue.

Issues that are blocked for a reason

Merge request is deployed to the canary environment.

QA is confirming whether it is a bug and its severity

Issues that are actively being worked on by a developer