Labels
Prioritized labels 11
Drag to reorder prioritized labels and change their relative priority.
-
(perceived) data lossGitLab.com / GitLab Infrastructure Team / Production EngineeringAn event that is seen as data loss from an external user
-
priority1GitLab.comWe will address this as soon as possible regardless of limit on our team capacity. See https://about.gitlab.com/handbook/engineering/quality/issue-triage/#priority
-
severity1GitLab.comBlocker - applies to bugs and bug categories of availability, performance, security and ux. See https://handbook.gitlab.com/handbook/engineering/infrastructure/engineering-productivity/issue-triage/#severity
-
severity2GitLab.comCritical - applies to bugs and bug categories of availability, performance, security and ux. See https://handbook.gitlab.com/handbook/engineering/infrastructure/engineering-productivity/issue-triage/#severity
-
priority2GitLab.compriority 2 We will address this soon and will provide capacity from our team for it in the next few releases. See https://about.gitlab.com/handbook/engineering/quality/issue-triage/#priority
-
priority3GitLab.comWe want to address this but may have other higher priority items. See https://about.gitlab.com/handbook/engineering/quality/issue-triage/#priority
-
priority4GitLab.comWe don't have visibility when this will be addressed. See https://about.gitlab.com/handbook/engineering/quality/issue-triage/#priority
-
unblocks othersGitLab.com / GitLab Infrastructure TeamWork that helps unblock other teams, often coming in as a request
Labels 4,145
-
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
-
automationGitLab.com / GitLab Infrastructure Team / Production EngineeringWhatever will improve on toil
-
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
-
availabilityGitLab.com / GitLab Infrastructure Team / Production EngineeringGitLab.com up is a better user experience
-
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.
-
backend-weight3GitLab.com(Medium) Features that are well understood and relatively straightforward. Bugs that are relatively poorly understood and may not yet have a suggested solution.
-
backend-weight4GitLab.com(Little more than Medium) Features that are well understood and slightly complex. Bugs that are loosely understood and without a suggested solution.
-
backend-weight5GitLab.com(Large) Features that are well understood, but known to be hard. Bugs that are very poorly understood, and will not have a suggested solution.