Prioritized Labels
Other Labels
  • Deliverable
    Issues scheduled for the current milestone.
  • Stretch
    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
    Getting idea to production running on Google Container Engine
  • customer success
    Input from customer success team
  • stewardship
    For issues related to the stewardship of GitLab
  • coach will finish
    Community contributions that have stalled, and need to be picked up by a merge request coach:
  • 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.
  • customer
    Issues that were reported by Enterprise Edition subscribers. This label should be accompanied by either the 'bug' or 'feature proposal' label
  • customer+
  • requires production access
    Bugs that result in support having to access the production Rails console or filesystem to fix.
  • Accepting merge requests
    Issues opened for contribution from the Community. Issue's weight is an estimation of complexity. Please mention @gitlab-org/coaches if you have any questions :)
  • federal
  • UX
    Issues for the UX team. Covers new or existing functionality that needs a design proposal
  • UX research
    Issues that require UX reseach
  • UI polish
    Visual improvement(s) to the existing user interface
  • Community contribution
    Issues that have been scheduled for an upcoming release and are actively being worked on by our community
  • OKR
  • bug
    Issues that report undesirable or incorrect behavior
    Please use the devops::plan label instead of this deprecated label. It is kept for historical issues.
  • documentation
    Epics, issues, and merge requests related to product documentation.