Skip to content

Prioritized labels

Drag to reorder prioritized labels and change their relative priority.
  • SL1
    GitLab.org
    Security Level 1 - Issues that present a critical security risk and must be patched before the next release
  • Scheduled
    GitLab.org / omnibus-gitlab
    Work that has been discussed and scheduled by the team.
  • Maintenance
    GitLab.org / omnibus-gitlab
    Change requests, eg. version upgrade of software, default configuration value change.
  • Internal
    GitLab.org / omnibus-gitlab
    Any work that is not customer/user facing.
  • Unscheduled
    GitLab.org / omnibus-gitlab
    Work that needs to be completed in a milestone but was not previously scheduled
  • Other labels

  • P1
    GitLab.org / omnibus-gitlab
  • cloud images
    GitLab.org / omnibus-gitlab
  • Meta
    GitLab.org / omnibus-gitlab
  • 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
  • Gitaly
    GitLab.org
    Issues for the Gitaly team
  • 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
  • aws
    GitLab.org / omnibus-gitlab
    Issues and MRs related to GitLab's AWS images
  • Bugs that result in support having to access the production Rails console or filesystem to fix.
  • kubernetes
    GitLab.org / omnibus-gitlab
  • Azure
    GitLab.org / omnibus-gitlab
  • qa
    GitLab.org / omnibus-gitlab