Labels
Prioritized labels 0
Drag to reorder prioritized labels and change their relative priority.
Labels 3,472
-
automation:ml wrongGitLab.orgIssues that were incorrectly triaged/labeled by AI https://gitlab.com/gitlab-org/quality/triage-ops/-/blob/master/policies/stages/report/untriaged-issues.yml
-
automation:prevent-auto-closeGitLab.orgLabel to prevent auto closure of issues and merge requests where applied
-
automation:quick-win-removedGitLab.orgWhen 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
-
automation:reviewers-remindedGitLab.orgThis label keeps track of Community contribution MRs where assigned reviewers have been reminded to review the MR
-
automation:self-triage-encouragedGitLab.orgTrack wider community issues where the author has been encouraged to self triage
-
automation:stale-remindedGitLab.orgIdentifies issues / merge requests that have been nudged by the stale reminder
-
automation:top-flaky-testGitLab.orgLabel for issues created by automation for the tests that are identified as most flaky.
-
availabilitylimitGitLab.orgGitLab, 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
-
awaiting feedbackGitLab.orgIssues that are blocked until more feedback is received from the reporter
-
backend completeGitLab.orgThe backend component of this piece of work has been completed, merged and verified.
-
backend-weight1GitLab.org(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.
-
backend-weight2GitLab.org(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.