Labels
Labels can be applied to issues, merge requests, and epics. Group labels are available for any project within the group.
Labels 3,860
-
priority 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
-
We want to address this but may have other higher priority items. See https://about.gitlab.com/handbook/engineering/quality/issue-triage/#priority
-
We don't have visibility when this will be addressed. See https://about.gitlab.com/handbook/engineering/quality/issue-triage/#priority
-
Label for issues relating to GitLab's product usage data (usage ping) and version check (version.gitlab.com).
-
Telemetry changes are reviewed and ready to be approved by Telemetry Maintainer
-
Product analytics changes require a review from product analytics review / maintainer.
-
Activities within the content strategy and ops team, within the product marketing org
-
Activities within the solutions marketing team, within the product marketing org
-
Used to identify all issues and epics related to the Cloud Sync Program
-
Product Security Risk Register: Minimal risk, routine monitoring sufficient. More details in: https://handbook.gitlab.com/handbook/security/security-assurance/security-risk/storm-program/#risk-drafting-guidance
-
Product Security Risk Register: Medium risk, within neutral tolerance. More details in: https://handbook.gitlab.com/handbook/security/security-assurance/security-risk/storm-program/#risk-drafting-guidance