Labels

This bug has had the default priority applied. Feel free to override. More info: gitlab-org/quality/triage-ops#29

The goal this milestone is to have: the engineering implementation plan for this issue created, a weight applied, and any priority or workflow labels added. If needed, this should be reviewed and approved by another engineer and/or product.

Priority 1 for the assigned milestone.

Priority 2 for the assigned milestone.

Priority 3 for the assigned milestone.

Priority 4 for the assigned milestone.

Issues which are particularly important to be released in the specified milestone. This should only be set by the responsible PM.

We will address this as soon as possible regardless of limit on our team capacity. See https://handbook.gitlab.com/handbook/product-development/how-we-work/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/product-development/how-we-work/issue-triage/#priority

We want to address this but may have other higher priority items. See https://handbook.gitlab.com/handbook/product-development/how-we-work/issue-triage/#priority

We don't have visibility when this will be addressed. See https://handbook.gitlab.com/handbook/product-development/how-we-work/issue-triage/#priority

Security issues is missing severity or priority label (automated label)