Skip to content

Prioritized labels 7

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/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
    Issues filed by specific customers. https://gitlab.com/gitlab-com/support/issues/31
  • regression
    GitLab.org / gitlab-runner
    Issues and changes related to regressions (introduced by non-patch releases)
  • bug
    GitLab.org
    Issues that report undesirable or incorrect behavior
  • 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

    • Labels 124

  • Needs confirmation
    GitLab.org / gitlab-runner
    Workflow: issues in a release that are generally done, but are waiting for final tests and/ore confirmation
  • Next Patch Release
    GitLab.org
    Issues to put in the next patch release. Work on these first, and add the Pick Into Stable label to the merge request, along with the appropriate milestone.
  • OKR
    GitLab.org
    https://about.gitlab.com/handbook/people-operations/okr/
  • P1
    GitLab.org
  • P2
    GitLab.org
  • P3
    GitLab.org
  • P4
    GitLab.org
  • Pick into Backports
    GitLab.org
    Merge requests that should be cherry-picked into previous releases
  • Pick into Stable
    GitLab.org
    Merge requests that should be cherry-picked into the ongoing release
  • Platform
    GitLab.org
    Issues for the Platform team. Covers everything that doesn't fall under the responsibility of one of the other teams
  • Prometheus
    GitLab.org
    Issues for the Prometheus team. Covers everything related to prometheus monitoring, including GitLab instances and user-applications
  • Release
    GitLab.org
    Issues for the Release team. Covers everything related to managing the monthly GitLab release
  • S1
    GitLab.org
  • S2
    GitLab.org
  • S3
    GitLab.org
  • S4
    GitLab.org
  • SL1
    GitLab.org
    Security Level 1 - Issues that present a critical security risk and must be patched before the next release
  • SL2
    GitLab.org
    Security Level 2 - Issues that present a moderate security risk and should be patched in the next Security Release if possible
  • SL3
    GitLab.org
    Security Level 3 - Issues that present a low security risk
  • SP1
    GitLab.org
    For internal Support team use.