Labels

Issues that were incorrectly triaged/labeled by AI https://gitlab.com/gitlab-org/quality/triage-ops/-/blob/master/policies/stages/report/untriaged-issues.yml

When the ~"quick win" label has been automatically removed because it doesn't meet the required criteria: https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#criteria-for-quick-win-issues

Identifies issues / merge requests that have been nudged by the stale reminder

GitLab, like most large applications, enforces limits within certain features. The absences of limits can impact security, performance, and availability. For this reason issues related to limits are considered as another category of ~"type::bug". https://about.gitlab.com/handbook/engineering/quality/issue-triage/#limit-related-bugs

(Trivial) The problem is very well understood, no extra investigation is required, the exact solution is already known and just needs to be implemented, no surprises are expected, and no coordination with other teams or people is required.

(Small) The problem is well understood and a solution is outlined, but a little bit of extra investigation will probably still be required to realize the solution.

(Medium) Features that are well understood and relatively straightforward. Bugs that are relatively poorly understood and may not yet have a suggested solution.

(Little more than Medium) Features that are well understood and slightly complex. Bugs that are loosely understood and without a suggested solution.

(Large) Features that are well understood, but known to be hard. Bugs that are very poorly understood, and will not have a suggested solution.

This work blocks other work

Any item that should prevent deployments to the Main stage of gstg (Staging) and gprd (Production) should have this label applied. This does NOT apply to the Canary stages of these environments.

Any item that should prevent feature-flag changes from proceeding should have this label applied.

A backwards-incompatible change that will need to be made with the next major release. See https://docs.gitlab.com/ee/development/contributing/index.html#breaking-changes

Business Technology Infrastructure - Access Requests

IT EntApps. Weekly Rolly update.

Issues impacting the availability of GitLab.com.

Functional defects resulting from feature changes