Prioritized Labels
Other Labels
  • Deliverable
    GitLab.org
  • Stretch
    GitLab.org
  • i2p-on-gke
    Getting idea to production running on Google Container Engine
    GitLab.org
  • customer success
    Input from customer success team
    GitLab.org
  • stewardship
    For issues related to the stewardship of GitLab
    GitLab.org
  • Gitaly
    Issues for the Gitaly team
    GitLab.org
  • coach will finish
    Community contributions that have stalled, and need to be picked up by a merge request coach: https://about.gitlab.com/jobs/merge-request-coach/
    GitLab.org
  • Next Patch Release
    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.
    GitLab.org
  • SP1
    For internal Support team use.
    GitLab.org
  • SP2
    For internal Support team use.
    GitLab.org
  • SP3
    For internal Support team use.
    GitLab.org
  • customer
    Issues that were reported by Enterprise Edition subscribers. This label should be accompanied by either the 'bug' or 'feature proposal' label
    GitLab.org
  • customer+
    GitLab.org
  • requires production access
    Bugs that result in support having to access the production Rails console or filesystem to fix.
    GitLab.org
  • Accepting Merge Requests
    GitLab.org
  • federal
    GitLab.org
  • UX
    Issues for the UX team. Covers new or existing functionality that needs a design proposal
    GitLab.org
  • UX ready
    Issues where the UX has been worked through and is ready to be scheduled
    GitLab.org
  • UX research
    Issues that require UX reseach
    GitLab.org
  • UI polish
    Visual improvement(s) to the existing user interface
    GitLab.org