Labels

Label to prevent duplicate notes from the triage-ops bot for bugs without a severity

Label to prevent duplicate notes from the triage-ops bot for customer bugs without a severity

Allows to disable the automated stage/group label inference: https://about.gitlab.com/handbook/engineering/quality/guidelines/triage-operations/#stage-and-group-labels-inference-from-category-labels

This label is applied to MRs where at least one reviewer has been awarded a Fast Review achievement.

Any merge requests authored by the automated `gitlab-housekeeper` gem https://gitlab.com/gitlab-org/gitlab/-/tree/master/gems/gitlab-housekeeper

Buggy/Incorrect/Wrong/Problematic merge requests authored by the automated `gitlab-housekeeper` gem https://gitlab.com/gitlab-org/gitlab/-/tree/master/gems/gitlab-housekeeper . Close them and add this label and we can later look into patterns of what is going wrong.

Issues triaged using AI- https://gitlab.com/gitlab-org/quality/triage-ops/-/blob/master/policies/stages/report/untriaged-issues.yml

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

Label to prevent auto closure of issues and merge requests where applied

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

This label keeps track of Community contribution MRs where assigned reviewers have been reminded to review the MR

Track wider community issues where the author has been encouraged to self triage

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

Label for issues created by automation for the tests that are identified as most flaky.

label for issues automatically created for top flaky specs

Label to prevent duplicate notes from the triage-ops bot.

Issues relating to automating tasks, bots, etc.

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