Skip to content

Prioritized labels

Drag to reorder prioritized labels and change their relative priority.

Other labels

  • SMB SalesTalent
    GitLab.com
    Topics related to talent development for SMB AEs
  • SMBEMEA
    GitLab.com
    SMB EMEA topics
  • SMI
    GitLab.com
    Senior Manager, Infrastructure
  • Used to track issues or epics that would need to be logged in the marketing, sales ops, or sales systems changelog to track major changes across functions
  • Used to track issues or epics that relate to temporary problems
  • SOC2
    GitLab.com
    Service Organization Control 2
  • SOX
    GitLab.com
    Sarbanes-Oxley
  • This label is used to indicate the control is under review to determine the appropriate SOX-Control State label
  • This label is used to indicate that Internal Audit testing has begun. If the results of the Internal Audit testing do not confirm Security Compliance’s belief the process is operating effectively, the control will go back into the Remediation state.
  • This label is used to indicate that the control has been tested by Internal Audit and confirmed to be operating effectively. Controls in this state need no further active work, but will need to be regularly tested to ensure they continue to operate effectively as we work towards an audit.
  • This label is used to indicate that the related control has been identified as a priority but we're not yet ready to start remediation because we're still trying to understand the scope and systems involved.
  • This label is used to indicate that the control has been tested by Security Compliance, confirmed to be operating effectively, and ready for the Internal Audit team to test. Controls in this state need no further active work from Security Compliance.
  • This label is used to indicate the Security Compliance team believes the control is “audit ready" but hasn't collected the evidence to validate that belief.
  • This label is used to indicate the Security Compliance team identified how the control is currently operating and sees areas to improve in order to get this control "audit ready".
  • This label is used to indicate that Security Compliance testing has begun and evidence exists that points to representative samples or other documentation being used to test operating effectiveness of the control. This is the phase where we will generate statistically-representative samples of the population relating to this control and validate that the process involved is working as expected. If the results of the test do not confirm our belief that the process is operating effectively, the control will go back into the Remediation state.
  • SRE:On-call
    GitLab.com
    DEPRECATED -- Use SRE:On-Call instead
  • SUSFY22 Q1 - Done
    GitLab.com
    This label indicates an issue or epic associated with improving SUS score is deployed to production.
  • This label indicates an issue or epic associated with improving SUS score is planned or in progress
  • SaaS Weekly
    GitLab.com
    Use this label to note issues that should be called out in the SaaS Weekly Call.