Labels

Used by engineering for research, prototyping, or proof of concept while investigating options for a planned deliverable

Issues related to any ongoing stage efficiency initiatives. Should be coupled with a devops::* stage label.

Issues that are currently being identified for auto-closure https://about.gitlab.com/handbook/engineering/quality/triage-operations/#auto-close-inactive-bugs

Issues and merge requests related to static analysis: Rubocop, Flay, HAML-lint, SCSS-lint, ES-lint, Brakeman, License finder, Config-lint, Bundle audit.

For issues related to the stewardship of GitLab

Issues related to managing the amount of storage consumed by groups and projects

Issues used to extract high level tasks from a main issue to split work between different stakeholders. A workaround until we have Parent <-> Child relationship..

Issues and MRs related to the subgroups feature

UXR issues that contain feedback from users regarding the improvement of an aspect of GitLab.

Used for tracking the number of support requests on the Issue Tracker (not for/by Support Team)

Needs to be assessed for ~"Customer Interest" in context of "Healthy Backlog" &18639

This is a temporary label tagged to work items which are need to fully support epic assignees workflows.

The label will prevent links being added to manage the issue via the contributor platform. See https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links

A temporary label for the AI Context task force

Issues related to personal task management