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
-
signals-engIncident-NotDetectedGitLab.comAdded by the Signals Engineering Team after an incident review determined the incident did not result from an alert
-
signals-engdevelopmentGitLab.comDevelopment work by the signals engineering team focused on building and enhancing detection tools, automation, and workflows that support security monitoring capabilities.
-
signals-engincident-detectedGitLab.comAdded by the Signals Engineering Team after an incident review determined the incident resulted from an alert
-
sprint-additionsGitLab.comThis issue was not originally in the sprint and was added after the sprint started.
-
sre-support-neededAnsibleGitLab.com / GitLab Infrastructure TeamThis task requires assistance of a SRE to deal with automation tasks through Ansible
-
sre-support-neededInfraGitLab.com / GitLab Infrastructure TeamThis task requires assistance of a SRE to deal with foundation infrastructure tasks, like Terraform, Chef, K8s, Observability (Prometheus or Grafana), Secrets (Vault or GKMS), etc.
-
staff+GitLab.com / GitLab Infrastructure TeamLabel used for assigned issues to staff+ engineerings