Labels can be applied to issues, merge requests, and epics. Group labels are available for any project within the group.
Labels
-
Part of the triage process for Create:Code Creation https://handbook.gitlab.com/handbook/engineering/development/dev/create/code-creation/milestone_planning/#planning-and-triage-process
-
Part of the triage process for Create:Code Creation https://handbook.gitlab.com/handbook/engineering/development/dev/create/code-creation/milestone_planning/#planning-and-triage-process
-
This label is used to track broken GDK incidents and their fixes.
-
Add this label when AppSec's SAST rules were helpful, informative, and/or not unhelpful. See https://gitlab.com/gitlab-com/gl-security/product-security/appsec/sast-custom-rules
-
Apply this label if AppSec's SAST rules were unhelpful and/or incorrect. See https://gitlab.com/gitlab-com/gl-security/product-security/appsec/sast-custom-rules
-
Added when automation has detected a SAST violation of GitLab's AppSec team's rules. See https://gitlab.com/gitlab-com/gl-security/product-security/appsec/sast-custom-rules
-
Designated for epics/issues that stem from the System Usability Scale (SUS) responder outreach calls. Issues labeled with "SUS Improvement" are typically aimed at enhancing the usability and user experience of our products/services based on feedback gathered from SUS surveys.
-
Web IDE issues which have NOT yet been prioritized into the current iteration or a future iteration.
-
Web IDE issues which HAVE been prioritized into the current iteration or a future iteration.
-
Web IDE issues that are being ignored from the current webide-workflow process and automation.
-
Web IDE issues which have already been closed in previous iterations
-
Issues related to visualization of CI pipelines, including pipeline graphs, pipeline dependencies for triggers, cross-project pipelines, and child/parent pipelines.
-
temporary label used to transition some issues from Growth to Fulfillment
Prioritized