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,137
-
changeGitLab.com / GitLab Infrastructure TeamAny change introduced to production that is not a deploy
-
changescheduledGitLab.com / GitLab Infrastructure TeamChange plans that are ready and scheduled for execution. See https://about.gitlab.com/handbook/engineering/infrastructure/change-management/.
-
chefGitLab.com / GitLab Infrastructure TeamThe guy that sets things on fire so we can eat them later
-
cincGitLab.com / GitLab Infrastructure TeamItems related to CINC configuration management infrastructure (open-source community supported distribution of Chef software)
-
closedstaleGitLab.comIssues that are being closed as inactive https://about.gitlab.com/handbook/engineering/quality/triage-operations/#auto-close-inactive-bugs
-
cloud nativeGitLab.com / GitLab Infrastructure Team / Production EngineeringSplitting the monolith and moving to a containerized world where different services scale independently
-
code-creation-triageneeds-reviewGitLab.comPart of the triage process for Create:Code Creation https://handbook.gitlab.com/handbook/engineering/development/dev/create/code-creation/milestone_planning/#planning-and-triage-process
-
code-creation-triagereviewedGitLab.comPart of the triage process for Create:Code Creation https://handbook.gitlab.com/handbook/engineering/development/dev/create/code-creation/milestone_planning/#planning-and-triage-process