Labels

Security issues is missing severity or priority label (automated label)

(Not yet implemented) Security implementation issues with this label will be considered for the next scheduled security release.

Security issue to be triaged by the AppSec team (automated label)

Instructs @gitlab-securitybot to skip the automation on this specific issue or MR

For items that are primarily related to self-managed instances

Label applied to merge requests that were approved and or merged by automation. Used for some Renovate MRs, among other things.

Blocker - 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

Critical - 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

Major - 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

Low - 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

Added by the Signals Engineering Team after an incident review determined the incident did not result from an alert

Signals Engineering Team - New detection created

Development work by the signals engineering team focused on building and enhancing detection tools, automation, and workflows that support security monitoring capabilities.

Added by the Signals Engineering Team after an incident review determined the incident resulted from an alert