Skip to content

Prioritized labels

Drag to reorder prioritized labels and change their relative priority.

Other labels

  • how-to
    GitLab.org / gollum-lib
  • 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
  • Bugs that result in support having to access the production Rails console or filesystem to fix.
  • UX
    GitLab.org
    Issues for the UX team. Covers new or existing functionality that needs a design proposal
  • UX ready
    GitLab.org
    Issues where the UX has been worked through and is ready to be scheduled
  • UX research
    GitLab.org
    Issues that require UX reseach