Labels can be applied to issues, merge requests, and epics. Group labels are available for any project within the group.
Labels
-
priority1GitLab.comWe will address this as soon as possible regardless of limit on our team capacity. See https://about.gitlab.com/handbook/engineering/quality/issue-triage/#priority
-
priority2GitLab.compriority 2 We will address this soon and will provide capacity from our team for it in the next few releases. See https://about.gitlab.com/handbook/engineering/quality/issue-triage/#priority
-
priority3GitLab.comWe want to address this but may have other higher priority items. See https://about.gitlab.com/handbook/engineering/quality/issue-triage/#priority
-
priority4GitLab.comWe don't have visibility when this will be addressed. See https://about.gitlab.com/handbook/engineering/quality/issue-triage/#priority
-
Pentest2018GitLab.comIssues for findings from a May 2018 penetration test from an external contractor
-
docsP4GitLab.comDocs Priority 4 - Low: Anything outside the next 3 releases (approx beyond one quarter).
-
keep confidentialGitLab.comThe 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.
-
typedirectionGitLab.comIssues for important features that are on our roadmap: https://about.gitlab.com/direction/
Prioritized