Labels can be applied to issues, merge requests, and epics. Group labels are available for any project within the group.
Labels
-
infrastructureGitLab.orgidentifies issues that may require assistance or support from GitLab's infrastructure team
-
infrastructure configurationGitLab.orgIssues for Infrastructure Configuration, part of the Configure stage of the DevOps lifecycle
-
infrastructure monitoringGitLab.orgIssues for Infrastructure Monitoring, part of the Monitor stage of the DevOps lifecycle
-
installationGitLab.orgIssues and merge requests related to installing GitLab: https://docs.gitlab.com/ee/install/
-
instrumentationGitLab.orgIssues that improve the measurability of how GitLab is being used by our customers. Please see our Telemetry Guide (https://docs.gitlab.com/ee/development/telemetry/).
-
internal customerGitLab.orgEpics and issues of interest for internal customers. See https://about.gitlab.com/handbook/product/product-processes/#internal-customers for more details.
-
iso29001::nist800-171notFederalGitLab.orgControl of Unclassified Information imposed by DoD onto its suppliers and contractors. Major requirement for Enterprise/Commercial organizations that contract or supply DoD.
-
isolationGitLab.orgIssues relating to creating an isolated environment for enterprises on gitlab.com
-
issue weightGitLab.orgRegards the EE product feature for adding weight to an issue: https://docs.gitlab.com/ee/workflow/issue_weight.html
-
k8s-platformGitLab.orgRelated to a single platform like okd, rke, eks, gke, ack, aks, k3s, kind, mirok8s, minikube
-
keep confidentialGitLab.orgThe content of the issue or comments contains to references to private user information, such as private repository paths and its contents should remain confidential indefinitely. This is usually primarily used for ~security or production issues.
-
knapsack_reportGitLab.orgIdentify spec performance issues created by gitlab-org/quality/engineering-productivity/team#354
Prioritized