Labels
Labels can be applied to issues, merge requests, and epics. Group labels are available for any project within the group.
Labels 3,733
-
Identifies issues and MRs dealing with improving the SEO for pages on gitlab.com
-
Issues related to projects created with the SHA-256 hashing algorithm
-
SIRT recommendation related to the implementation or improvement of security controls
-
SIRT recommendation related to detecting and alerting malicious activity
-
SIRT recommendation related to the implementation or improvement of processes and procedures
-
Vulnerability issues that have breached remediation SLO. Previously titled as Remediation SLO::Breach
-
Identify vulnerability issues which will breach the remediation SLO in 2 weeks. Previously titled as Remediation SLO::Near Breach
-
Label to signify that a bug issue has missed its targeted SLO (Service Level Objective). See https://docs.gitlab.com/ee/development/contributing/issue_workflow.html#priority-labels. Previously titled as missed-SLO
-
Label to signify that a bug issue is approaching the SLO for applied severity. Previously titled as approaching-SLO
-
Related to Subscription Management feature of Billing Account Management