Labels

Labels to identify epics @abuango is working on

Issue is awaiting action from engineering (or is currently being worked on by engineering).

Issue is awaiting action by the requestor (more information, confirmation etc).

Issues marked to be part of the AI Spring Cleaning effort #2653

Related to the spamcheck anti-spam service.

https://gitlab.com/gitlab-com/gl-security/appsec/tooling/assistant

https://gitlab.com/gitlab-com/gl-security/appsec/tooling/assistant

Add this label when AppSec's Depscore comments were helpful. See https://gitlab.com/gitlab-com/gl-security/product-security/appsec/tooling/depscore

Label used on MR's that introduced a vulnerability. It is used for metrics for the AppSec team: gitlab-com/content-sites/handbook!11439

Denotes issues used for the security release process retrospective in the Application Security team

Issues triaged using AI- https://gitlab.com/gitlab-org/quality/triage-ops/-/blob/master/policies/stages/report/untriaged-issues.yml

Issues that were incorrectly triaged/labeled by AI https://gitlab.com/gitlab-org/quality/triage-ops/-/blob/master/policies/stages/report/untriaged-issues.yml

When the ~"quick win" label has been automatically removed because it doesn't meet the required criteria: https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#criteria-for-quick-win-issues

Identifies issues / merge requests that have been nudged by the stale reminder

GitLab, like most large applications, enforces limits within certain features. The absences of limits can impact security, performance, and availability. For this reason issues related to limits are considered as another category of ~"type::bug". https://about.gitlab.com/handbook/engineering/quality/issue-triage/#limit-related-bugs