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

Issues that are blocked until more feedback is received from the reporter

Issues related to the Award Emoji feature on issues and merge requests.

Amazon Web Services

Issues that require backend work

The backend component of this piece of work has been completed, merged and verified.

(Trivial) The problem is very well understood, no extra investigation is required, the exact solution is already known and just needs to be implemented, no surprises are expected, and no coordination with other teams or people is required.

(Small) The problem is well understood and a solution is outlined, but a little bit of extra investigation will probably still be required to realize the solution.

(Medium) Features that are well understood and relatively straightforward. Bugs that are relatively poorly understood and may not yet have a suggested solution.

(Little more than Medium) Features that are well understood and slightly complex. Bugs that are loosely understood and without a suggested solution.

(Large) Features that are well understood, but known to be hard. Bugs that are very poorly understood, and will not have a suggested solution.

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