Skip to content

Prioritized labels

Drag to reorder prioritized labels and change their relative priority.

Other labels

  • i2p-on-gke
    GitLab.org
    Getting idea to production running on Google Container Engine
  • customer success
    GitLab.org
    Input from customer success team
  • stewardship
    GitLab.org
    For issues related to the stewardship of GitLab
  • coach will finish
    GitLab.org
    Community contributions that have stalled, and need to be picked up by a merge request coach: https://about.gitlab.com/jobs/merge-request-coach/
  • 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.
  • SP1
    GitLab.org
    For internal Support team use.
  • SP2
    GitLab.org
    For internal Support team use.
  • SP3
    GitLab.org
    For internal Support team use.
  • 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
  • Bugs that result in support having to access the production Rails console or filesystem to fix.
  • Issues that have been scheduled for an upcoming release and are actively being worked on by people from the community
  • 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