Skip to content

Prioritized labels

Drag to reorder prioritized labels and change their relative priority.

Other labels

  • vagrant
    GitLab.org / Cookbook GitLab
  • bundle
    GitLab.org / Cookbook GitLab
  • development
    GitLab.org / Cookbook GitLab
  • centos
    GitLab.org / Cookbook GitLab
  • eric
    GitLab.org / Cookbook GitLab
  • improvement
    GitLab.org / Cookbook GitLab
  • cookbook
    GitLab.org / Cookbook GitLab
  • ubuntu
    GitLab.org / Cookbook GitLab
  • Deliverable
    GitLab.org
    Issues scheduled for the current milestone.
  • Stretch
    GitLab.org
    Issues that are a stretch goal for delivering in the current milestone. If these issues are not done in the current release, they will strongly be considered for the next release.
  • 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/job-families/expert/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.
  • 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
    Features and bugs reported by large enterprise customers. This label is in use by the product org, please post in #product Slack channel if you have questions.
  • Bugs that result in support having to access the production Rails console or filesystem to fix.
  • [deprecated] Please use "Seeking community contributions" instead. gitlab-org/developer-relations/contributor-success/team-task#77