Skip to content

Prioritized labels

Drag to reorder prioritized labels and change their relative priority.
  • security
    GitLab.org
    Issues related to the security of GitLab or its dependencies. Please report vulnerabilities responsibly per https://about.gitlab.com/security/disclosure/
  • customer
    GitLab.org
    Issues that were reported by Enterprise Edition subscribers. This label should be accompanied by either the 'bug' or 'feature proposal' label
  • customer+
    GitLab.org
    Features and bugs reported by large enterprise customers. This label is in use by the product org, please post in #product Slack channel if you have questions.
  • regression
    GitLab.org
    Issues with this label are regressions from the previous non-patch release
  • typebug
    GitLab.org
    Issues that report undesirable or incorrect behavior. See https://about.gitlab.com/handbook/engineering/metrics/#work-type-classification
  • direction
    GitLab.org
    Issues for important features that are on our roadmap: https://about.gitlab.com/direction/
  • high priority
    GitLab.org / gitlab-runner
    Other important issues

    • Other labels

  • runner-distribution
    GitLab.org / gitlab-runner
    Issues related to runner distribution such as building & publishing binaries/images
  • runner-distributionlabs
    GitLab.org / gitlab-runner
    Issues related to runner distribution for the Labs section
  • runner-kubernetes-operator
    GitLab.org / gitlab-runner
    For tracking issues and merge requests related to the GitLab Runner Operator for Kubernetes
  • runnercore
    GitLab.org / gitlab-runner
  • safe-to-retry
    GitLab.org
    This label was created by group::database to indicate MRs that are safe to retry, specifically around PK migration MRs
  • saml
    GitLab.org
    Issues related to integration with SAML: http://doc.gitlab.com/ce/integration/saml.html
  • scaled migrations
    GitLab.org
    For issues related to large migrations performed by our importers. This should only be used by group::import and integrate
  • scaling-direction
    GitLab.org
    Issues and epics that describe potential ways to scale GitLab further
  • schema redesign
    GitLab.org
  • scim
    GitLab.org
    Issues related to the GitLab SCIM API https://docs.gitlab.com/ee/api/scim.html
  • scm-backlog
    GitLab.org
  • sec-decomposition
    GitLab.org
    Issues that have been identified for inclusion in https://handbook.gitlab.com/handbook/company/working-groups/secure-govern-database-decomposition/
  • sec-planningcomplete
    GitLab.org
    https://about.gitlab.com/handbook/security/security-engineering-and-research/application-security/appsec-reviews.html#quantifying-interactions
  • sec-planningin-progress
    GitLab.org
    https://about.gitlab.com/handbook/security/security-engineering-and-research/application-security/appsec-reviews.html#quantifying-interactions
  • sec-planningno-action
    GitLab.org
    https://about.gitlab.com/handbook/security/security-engineering-and-research/application-security/appsec-reviews.html#quantifying-interactions
  • sec-planningpending-followup
    GitLab.org
    https://about.gitlab.com/handbook/security/security-engineering-and-research/application-security/appsec-reviews.html#quantifying-interactions
  • secauto
    GitLab.org
  • secautoblocked
    GitLab.org
  • secautoin-progress
    GitLab.org
  • secautoready
    GitLab.org