Web IDE issues which have already been closed in previous iterations

Web IDE issues that are being ignored from the current webide-workflow process and automation.

Web IDE issues which HAVE been prioritized into the current iteration or a future iteration.

Web IDE issues which have NOT yet been prioritized into the current iteration or a future iteration.

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.

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

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

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

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.

This label is used to track broken GDK incidents and their fixes.

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

Issues for the Test Platform sub-department: https://handbook.gitlab.com/handbook/engineering/infrastructure/test-platform/

Unhealthy test issues with less than 12 slowness reports.

Unhealthy test issues with between 12 and 27 slowness reports.

Unhealthy test issues with between 28 and 39 slowness reports.

Unhealthy test issues with 40 or more slowness reports.