Other labels
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.
SUSFY22 Q1 - Done
GitLab.org
This label indicates an issue or epic associated with improving SUS score is deployed to production.
SUSFY22 Q1 - Incomplete
GitLab.org
This label indicates an issue or epic associated with improving SUS score is planned or in progress
SUSFY22 Q2 - Done
GitLab.org
This label indicates an issue or epic associated with improving SUS score is deployed to production.
SUSFY22 Q2 - Incomplete
GitLab.org
This label indicates an issue or epic associated with improving SUS score is planned or in progress in Q2
SUSImpacting
GitLab.org
For tracking SUS(System Usability Scale)-impacting issues (https://about.gitlab.com/handbook/engineering/ux/performance-indicators/#sus-impacting-issues-openedclosed-each-month)
SUSNon-impacting
GitLab.org
Used to avoid SUS-related tracking efforts, mostly for new feature UI development work
SUSResponder Outreach
GitLab.org
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.
SecOps-Priority1
GitLab.org
A label to denote the priority of issues related to the Security Operations T&S and SIRT OKR gitlab-com/gl-security/security-department-meta#1392
SecOps-Priority2
GitLab.org
A label to denote the priority of issues related to the Security Operations T&S and SIRT OKR gitlab-com/gl-security/security-department-meta#1392
Prioritized