Skip to content

Prioritized labels

Drag to reorder prioritized labels and change their relative priority.
  • workflow
    GitLab.com / GitLab Infrastructure Team / delivery
  • infrastructure
    GitLab.com / GitLab Infrastructure Team / delivery
  • Other labels

  • 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.
  • SalesDev
    GitLab.com
    General tag for any issue that needs SDR attention, request for work and/or involvement
  • SalesOPS
    GitLab.com
    This Tag is used to flag things up for the SalesOps Team to see
  • Issue has been put on hold due to End of the Quarter
  • SalesOPsScoping
    GitLab.com
    Gathering requirements to determine if the request will be assigned or declined
  • Used to track issues or epics that would need to be logged in the sales operations changelog to track major changes
  • SalesOps RingLead
    GitLab.com
    Label used to track issues and Epic involving our third party deduping tool RingLead
  • This label is being used to track the Territory Management: Epic, child epics and issues
  • SalesOpsAssigned
    GitLab.com
    Sales Ops requests that are assigned
  • SalesOpsBacklog
    GitLab.com
    Sales Ops requests that are submitted but have not been reviewed or assigned.
  • SalesOpsCompleted
    GitLab.com
    Sales Ops requests that are completed