Labels

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

Issues that are blocked until more feedback is received from the reporter

Issues related to the emoji reactions feature on issues and merge requests.

Amazon Web Services

Used by AWS to indicate approval

Used by AWS to indicate approval

Issues that require backend work

The backend component of this piece of work has been completed, merged and verified.

(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.

Issues that are created by invalid users Labels created to support the Healthy backlog Initiative (link - to be updated when published)

Issues without any activity for 36+ months Labels created to support the Healthy backlog Initiative (link - to be updated when published)

Issues describes a bug, feature or maintenance effort that is not in line with GitLab strategy or GitLab team members cannot take on in the next 18 months. They may or may not be closed depending on the input from the community, customers and GitLab team members. Labels created to support the Healthy backlog Initiative (link - to be updated when published)

Indicates that issues describes a bug, feature or maintenance effort that is in line with GitLab strategy and GitLab team members can take it on in the next 18 months. These issues will stay open and should be updated regularly (at least once every 6 months). Labels created to support the Healthy backlog Initiative (link - to be updated when published)

Issues that are marked for closure - with some time delay to allow for input by community, customer and gitlab team members that will determine if they get closed or stay open. Labels created to support the Healthy backlog Initiative (link - to be updated when published)

Indicates which maintenance issues should be included in the bug triage - as part of the regular triage process, the backlog scoped label should be modified to either prospective if committed, or no-commitment if not committed to, as well as with a severity label Labels created to support the Healthy backlog Initiative (link - to be updated when published)

Added to MRs that are backports to stable branches. Allows milestone changing automation to skip. See gitlab-org/quality/triage-ops!3450.