You need to sign in or sign up before continuing.
Labels can be applied to issues, merge requests, and epics. Group labels are available for any project within the group.
Labels
-
team activitiesGitLab.orgItems that are related to CI/CD UX team activities and need attention / feedback from the members.
-
support requestGitLab.orgUsed for tracking the number of support requests on the Issue Tracker (not for/by Support Team)
-
suggested improvements uxrGitLab.orgUXR issues that contain feedback from users regarding the improvement of an aspect of GitLab.
-
sub-issueGitLab.orgIssues used to extract high level tasks from a main issue to split work between different stakeholders. A workaround until we have Parent <-> Child relationship..
-
storage-managementGitLab.orgIssues related to managing the amount of storage consumed by groups and projects
-
static code analysisGitLab.orgIssues and merge requests related to static analysis: Rubocop, Flay, HAML-lint, SCSS-lint, ES-lint, Brakeman, License finder, Config-lint, Bundle audit.
-
staleGitLab.orgIssues that are currently being identified for auto-closure https://about.gitlab.com/handbook/engineering/quality/triage-operations/#auto-close-inactive-bugs
-
stage-efficiencyGitLab.orgIssues related to any ongoing stage efficiency initiatives. Should be coupled with a devops::* stage label.
-
spikeGitLab.orgUsed by engineering for research, prototyping, or proof of concept while investigating options for a planned deliverable
Prioritized