Labels

Issues that are marked for closure - with some time delay to allow for input by community, customer and gitlab team members that will determine if they get closed or stay open. Please do not add this label manually - it is for bulk closure efforts. Labels created to support the Healthy backlog Initiative (blog: https://about.gitlab.com/blog/inside-gitlabs-healthy-backlog-initiative/ & tracking issue: https://gitlab.com/groups/gitlab-org/-/epics/18252

Indicates which maintenance issues should be included in the bug triage - as part of the regular triage process, the backlog scoped label should be modified to either prospective if committed, or no-commitment if not committed to, as well as with a severity label Labels created to support the Healthy backlog Initiative (blog: https://about.gitlab.com/blog/inside-gitlabs-healthy-backlog-initiative/ & tracking issue: https://gitlab.com/groups/gitlab-org/-/epics/18252

Added to MRs that are backports to stable branches. Allows milestone changing automation to skip. See gitlab-org/quality/triage-ops!3450.

This label is added if this MR has been successfully backported

This label is added if this MR needs to be backported

This label is added if this MR does not need to be backported

See https://about.gitlab.com/handbook/engineering/metrics/#data-classification

Issues related to our GitLab Flavored Markdown rendering pipeline, Banzai: https://en.wikipedia.org/wiki/Banzai_Pipeline

Issues belonging to the Collection and Data Exfiltration stage of a Breach and Attack Simulation exercise. See https://about.gitlab.com/handbook/engineering/incubation/breach-and-attack-simulation/#collection--data-exfiltration

Issues belonging to the Command and Control (C2) stage of a Breach and Attack Simulation exercise. See https://about.gitlab.com/handbook/engineering/incubation/breach-and-attack-simulation/#command--control

Issues Destruction stage of a Breach and Attack Simulation exercise. See https://about.gitlab.com/handbook/engineering/incubation/breach-and-attack-simulation/#destruction-simulated

Issues belonging to the External Penetration stage of a Breach and Attack Simulation exercise. See https://about.gitlab.com/handbook/engineering/incubation/breach-and-attack-simulation/#external-penetration

Issues belonging to the Lateral Movement stage of a Breach and Attack Simulation exercise. See https://about.gitlab.com/handbook/engineering/incubation/breach-and-attack-simulation/#lateral-movement

Issues belonging to the Privilege Escalation stage of a Breach and Attack Simulation exercise. See https://about.gitlab.com/handbook/engineering/incubation/breach-and-attack-simulation/#privilege-escalation

Issues belonging to the Reconnaissance stage of a Breach and Attack Simulation exercise. See https://about.gitlab.com/handbook/engineering/incubation/breach-and-attack-simulation/#recon

basic search refers to searches that are not handled by Elasticsearch. Its counter part is advanced search

This flag will be used for issues where the fix has been implemented but is pending activation via a feature flag which will be tracked through a different issue.

Used by teams that want to designate an issue as blocked without changing the workflow scoped label

Blocked pending architectural refactor or design changes.