Labels can be applied to issues, merge requests, and epics. Group labels are available for any project within the group.
Labels
-
staleGitLab.orgIssues that are currently being identified for auto-closure https://about.gitlab.com/handbook/engineering/quality/triage-operations/#auto-close-inactive-bugs
-
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.
-
storage-managementGitLab.orgIssues related to managing the amount of storage consumed by groups and projects
-
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..
-
suggested improvements uxrGitLab.orgUXR issues that contain feedback from users regarding the improvement of an aspect of GitLab.
-
support requestGitLab.orgUsed for tracking the number of support requests on the Issue Tracker (not for/by Support Team)
-
team activitiesGitLab.orgItems that are related to CI/CD UX team activities and need attention / feedback from the members.
-
teamDeliveryGitLab.orgIssues for the Delivery team: https://about.gitlab.com/handbook/engineering/infrastructure/team/delivery/#delivery
-
teamFoundationsGitLab.orgWork related to the Infrastructure Production Engineering Foundations team.
-
teamFrameworksGitLab.orgScalability:Frameworks team https://about.gitlab.com/handbook/engineering/infrastructure/team/scalability
Prioritized