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
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+
Issues filed by specific customers. https://gitlab.com/gitlab-com/support/issues/31
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
Community Contribution
Issues that have been scheduled for an upcoming release and are actively being worked on by people from the community
GitLab.org
OKR
SL1
Security Level 1 - Issues that present a critical security risk and must be patched before the next release
GitLab.org
SL2
Security Level 2 - Issues that present a moderate security risk and should be patched in the next Security Release if possible
GitLab.org
SL3
Security Level 3 - Issues that present a low security risk
GitLab.org
Prioritized label