Labels can be applied to issues, merge requests, and epics. Group labels are available for any project within the group.
Labels
-
securitybotignoreGitLab.comInstructs @gitlab-securitybot to skip the automation on this specific issue or MR
-
severity1GitLab.comBlocker - applies to bugs and bug categories of availability, performance, security and ux. See https://about.gitlab.com/handbook/engineering/quality/issue-triage/#severity
-
severity2GitLab.comCritical - applies to bugs and bug categories of availability, performance, security and ux. See https://about.gitlab.com/handbook/engineering/quality/issue-triage/#severity
-
severity3GitLab.comMajor - applies to bugs and bug categories of availability, performance, security and ux. See https://about.gitlab.com/handbook/engineering/quality/issue-triage/#severity
-
severity4GitLab.comLow - applies to bugs and bug categories of availability, performance, security and ux. See https://about.gitlab.com/handbook/engineering/quality/issue-triage/#severity
-
sprint-additionsGitLab.comThis issue was not originally in the sprint and was added after the sprint started.
-
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
Prioritized