Other labels
severity4
GitLab.com
Low - applies to bugs and bug categories of availability, performance, security and ux. See https://about.gitlab.com/handbook/engineering/quality/issue-triage/#severity
severity3
GitLab.com
Major - applies to bugs and bug categories of availability, performance, security and ux. See https://about.gitlab.com/handbook/engineering/quality/issue-triage/#severity
severity2
GitLab.com
Critical - applies to bugs and bug categories of availability, performance, security and ux. See https://about.gitlab.com/handbook/engineering/quality/issue-triage/#severity
severity1
GitLab.com
Blocker - applies to bugs and bug categories of availability, performance, security and ux. See https://about.gitlab.com/handbook/engineering/quality/issue-triage/#severity
securitybotignore
GitLab.com
Instructs @gitlab-securitybot to skip the automation on this specific issue or MR
security-target
GitLab.com
(Not yet implemented) Security implementation issues with this label will be considered for the next scheduled security release.
security-sp-label-missing
GitLab.com
Security issues is missing severity or priority label (automated label)
security-set-milestone
GitLab.com
Security issue needs a milestone with (future) dates (automated label)
security-notifications
GitLab.com
Subscribes the issue for automatic notifications related to security releases. This label is meant for use on Security Implementation Issues on the security mirror projects.
security-department-meta
GitLab.com / GitLab Security Department
For issues relevant to the whole Security Department
security-champions
GitLab.com
In relation with the Security Champions Program - https://about.gitlab.com/handbook/engineering/security/security-champions-program.html
Prioritized