Labels
Prioritized labels 0
Drag to reorder prioritized labels and change their relative priority.
Labels 3,967
-
[deprecated] grouphosted runnersGitLab.comDeprecated. See [team::Runners Platform](https://handbook.gitlab.com/handbook/engineering/infrastructure-platforms/production-engineering/runners-platform/)
-
about.gitlab.comGitLab.comRebecca Reich 2021-02-09 label for the distribution channel of the marketing website
-
actionableengineeringGitLab.comIssue is awaiting action from engineering (or is currently being worked on by engineering).
-
actionablerequestorGitLab.comIssue is awaiting action by the requestor (more information, confirmation etc).
-
ansibleGitLab.com / GitLab Infrastructure TeamIssues/MRs relating to the use of Ansible within our environment.
-
appsec-kpivulnerability-introducedGitLab.comLabel used on MR's that introduced a vulnerability. It is used for metrics for the AppSec team: gitlab-com/content-sites/handbook!11439
-
appsecSecurity Release retroGitLab.comDenotes issues used for the security release process retrospective in the Application Security team
-
automation:ml wrongGitLab.comIssues that were incorrectly triaged/labeled by AI https://gitlab.com/gitlab-org/quality/triage-ops/-/blob/master/policies/stages/report/untriaged-issues.yml
-
automation:quick-win-removedGitLab.comWhen 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:stale-remindedGitLab.comIdentifies issues / merge requests that have been nudged by the stale reminder
-
availabilitylimitGitLab.comGitLab, 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
-
backend-weight1GitLab.com(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.com(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.