Bug which is founded in feature test (with type::bug label) or qa feature test task

The handbook write and maintaince work

Task related to performance test

Bug which is founded in quality pipeline (with type::bug label) or qa pipeline oncall task

Bugs which is founded in regression (with type::bug label) or QA regression task

Used to create a major/minor/patch/security release

Used for research, prototyping, or proof of concept while investigating options for a planned deliverable

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