We will address this soon and will provide capacity from our team for it in the next few releases. See https://about.gitlab.com/handbook/engineering/quality/issue-triage/#priority

We want to address this but may have other higher priority items. See https://about.gitlab.com/handbook/engineering/quality/issue-triage/#priority

We don't have visibility when this will be addressed. See https://about.gitlab.com/handbook/engineering/quality/issue-triage/#priority

Issue related to production env

All issues which are related to qa automation work

Work related to bug refinement

Work to support other teams.

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