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,126
-
workflow-infraTriage-estimatingGitLab.com / GitLab Infrastructure TeamTriage estimating is a step after opened to have the team estimate and break down the item.
-
workflow-infraUnder ReviewGitLab.com / GitLab Infrastructure TeamIssue is waiting on approval or peer review
-
workflow-infraVerifyGitLab.com / GitLab Infrastructure TeamVerify is a state after in-progress, before closed to make sure the work is done.
-
workflow-infraWaitingGitLab.com / GitLab Infrastructure TeamItems that are in progress, but waiting on external feedback from a Vendor (GCP, Cloudflare ticket)
-
workflow-infrainput_requestedGitLab.com / GitLab Infrastructure TeamFor issues that require input from members of the Reliability team
-
workflow-infrafinBlockedGitLab.comIndicated that this issue can not be progressed any further without removing the blocking issue
-
workflow-infrafinConceptGitLab.comideas for how to tackle the issue actively being discussed in comments
-
workflow-infrafinImplementation In ProgressGitLab.comIndicates that the fix or feature is currently being implemented
-
workflow-infrafinStalledGitLab.comIndicates the issue has voluntary been put on hold because work is being done on higher priority items
-
workflow-infrafinVerifyGitLab.comverify that the work is completed and the impact is within expectations
-
workflow-vmblockedGitLab.comScoped label to indicate Vulnerability management work item is in scoped stage
-
workflow-vmcompleteGitLab.comScoped label to indicate Vulnerability management work item is in scoped stage
-
workflow-vmin-progressGitLab.comScoped label to indicate Vulnerability management work item is in scoped stage
-
workflow-vmreadyGitLab.comScoped label to indicate Vulnerability management work item is in scoped stage
-
workflow-vmtriageGitLab.comScoped label to indicate Vulnerability management work item is in triage stage
-
workflowcompleteGitLab.comApplied after all MRs have merged and the issue has been verified if necessary