Labels can be applied to issues, merge requests, and epics. Group labels are available for any project within the group.
Labels
-
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
-
kubernetes-migration-blockerGitLab.orgUsed to track issues within gitlab-org group that need to be resolved in order for gl-infra to proceed with their migration to kubernetes
-
labelsGitLab.orgIssues related to the Labels feature on issues and merge requests: https://docs.gitlab.com/ee/user/project/labels.html
-
language or package manager supportGitLab.orgAdd or improve the support for specific languages, language versions, package managers, or package manager versions
-
ldapGitLab.orgIssues related to integration with LDAP: http://doc.gitlab.com/ee/integration/ldap.html
-
license checkGitLab.orgFor issues related to the license check/license management functionality - NOT related to billing/licensing.
-
licensing 💌GitLab.orgIssues related to the Enterprise Edition license: http://doc.gitlab.com/ee/license/README.html and the user experience of managing GitLab license keys.
-
linked-issueGitLab.orgUsed to highlight merge requests linked to one or more issues. For easily determining hackathon point calculations. Automatically applied by https://gitlab.com/gitlab-org/community-relations/contributor-success/toolbox
-
linter requestGitLab.orgThis label means this issue proposal about adding a lint to our codebase is being requested
Prioritized