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,221
-
StORMBlockedGitLab.comNo further action can be performed. Support is required. Assignee should be the individual on point for escalation.
-
StORMIntakeGitLab.comLabel to communicate potential security operational risks to the Security Risk Team
-
StORMNeeds Additional InformationGitLab.comAdditional information is required to support the Security Risk Team's StORM Risk Assessment
-
StORMNot StartedGitLab.comThis label indicates that the associated issue is ready to be actioned. The owner should be the person on point.
-
StORMOut of ScopeGitLab.comThe Security Risk Team performed a StORM Risk Assessment and determined that the potential risk identified is out of scope for the StORM program because it is not considered an operational security risk.
-
StORMQAGitLab.comIssues (such as Risk Treatment) requiring manager or peer review should be added to this label and assigned to the reviewer prior to closure.
-
StORMScheduledGitLab.comSecRisk utilizes this label to identify issues that have a due date but do not require action from Security Engineers at this time (such as risk treatments).
-
StORMUnder AssessmentGitLab.comLabel used to note the Security Risk Team is currently assessing a potential risk