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,129
-
staleGitLab.comIssues that are currently being identified for auto-closure https://about.gitlab.com/handbook/engineering/quality/triage-operations/#auto-close-inactive-bugs
-
statusinactiveGitLab.comFor issues that are inactive and not being worked on in the current quarter
-
statusplanGitLab.comused in conjunction with sales enablement sessions to indicate when a session topic has been prioritized but not yet scheduled
-
statusscheduledGitLab.comused in conjunction with sales enablement sessions to indicate when a session topic has been prioritized and scheduled
-
strategyGitLab.complans, methods, or series of maneuvers or stratagems for obtaining specific goals or results
-
tShirt-sizeLGitLab.com / GitLab Infrastructure Team / Production EngineeringTime estimated is 1 month or less
-
tShirt-sizeMGitLab.com / GitLab Infrastructure Team / Production EngineeringTime estimated is 1 week or less
-
tShirt-sizeSGitLab.com / GitLab Infrastructure Team / Production EngineeringTime estimated is 1 day or less
-
tShirt-sizeXLGitLab.com / GitLab Infrastructure Team / Production EngineeringTime estimated is more than 1 month