Skip to content

Prioritized labels

Drag to reorder prioritized labels and change their relative priority.

Other labels

  • flakiness1
    GitLab.org
    Unhealthy test issues with 42 or more flakiness reports.
  • flakiness2
    GitLab.org
    Unhealthy test issues with between 22 and 41 flakiness reports.
  • flakiness3
    GitLab.org
    Unhealthy test issues with between 4 and 21 flakiness reports.
  • flakiness4
    GitLab.org
    Unhealthy test issues with less than 4 flakiness reports.
  • slowness1
    GitLab.org
    Unhealthy test issues with 40 or more slowness reports.
  • slowness2
    GitLab.org
    Unhealthy test issues with between 28 and 39 slowness reports.
  • slowness3
    GitLab.org
    Unhealthy test issues with between 12 and 27 slowness reports.
  • slowness4
    GitLab.org
    Unhealthy test issues with less than 12 slowness reports.
  • gdk:broken
    GitLab.org
    This label is used to track broken GDK incidents and their fixes.
  • 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.
  • appsec-sasthelpful
    GitLab.org
    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
  • SUS Survey
    GitLab.org
    Issues and epics labeled with "SUS Survey" are directly associated with the administration, analysis, or outcomes of the System Usability Scale (SUS) survey. This label is utilized for tracking tasks related to planning, conducting, or evaluating SUS surveys.
  • Web IDE issues which have NOT yet been prioritized into the current iteration or a future iteration.