Skip to content

Prioritized labels 0

Drag to reorder prioritized labels and change their relative priority.

Labels 3,036

  • Appsec team - a team member is reviewing this issue
  • Appsec team - Issue determined eligible for risk acceptance as determined by backlog review
  • Appsec team - Valid security issue as determined during backlog review
  • When applied to Confidential ~security issues indicates that public/canonical Merge Requests can be opened against it.
  • Security issue is missing a group:: label (automated label)
  • Security issue has been escalated (automated label)
  • 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-release
    GitLab.org
    Issues for improving security release workflow
  • Security issue needs a milestone with (future) dates (automated label)
  • Security issues is missing severity or priority label (automated label)
  • security-target
    GitLab.org
    Security implementation issues with this label will be automatically considered for the next scheduled security release. The evaluation runs around the top of each hour.
  • Security issue to be triaged by the AppSec team (automated label)
  • securitybotignore
    GitLab.org
    Instructs @gitlab-securitybot to skip the automation on this specific issue or MR
  • self-managed
    GitLab.org
    For items that are primarily related to self-managed instances
  • service-component
    GitLab.org
    Relating to Services that make up GitLab
  • settings
    GitLab.org
    Issues related to project, group, profile, or application settings
  • severity1
    GitLab.org
    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