Gitlab hero border pattern left svg Gitlab hero border pattern right svg


Scope of Support for GitLab Self-managed (Starter, Premium, Ultimate licenses)

GitLab Support will help troubleshoot all components bundled with GitLab Omnibus when used as a packaged part of a GitLab installation. Any assistance with modifications to GitLab, including new functionality, bug-fixes, issues with alpha features or other code changes should go through the GitLab issue tracker, triage, and release cycle.

Support is not offered for local modifications to GitLab source code.

Your Support Contract will cover support for Beta features. We will automatically triage tickets for Beta features with the lowest priority available.

We understand that GitLab is often used in complex environments in combination with a variety of tools. We'll do best-effort support in debugging components that work alongside GitLab.

Unless otherwise specified in your support contract, we support the current major version and previous two major versions only. As of writing, GitLab installations running versions in the 11.x, 10.x and 9.x series are eligible for support.

Note: If you obtained an Ultimate license as part of GitLab's Open Source or Education programs, Support (as included with Starter, Premium or Ultimate licenses) is not included unless purchased separately. Please see the GitLab OSS License/Subscription Details for additional details

Differences between Suppport Tickets and GitLab Issues

It's useful to know the difference between a support ticket ( vs. an issue on (e.g.

For customers with a plan that includes ticketed Support, always feel free to contact support with your issue in the first instance via This is the primary channel the Support team uses to interact with customers and it is the only channel that is based on an SLA. Here GitLab support team will gather the necessary information and help debug an issue. In many cases we can find a resolution without requiring input from the development team. However, sometimes the debugging will uncover a bug in GitLab itself or that some new feature or enhancement is necessary for your use-case.

This is when we create an issue on - whenever input is needed from developers to investigate an issue further, to fix a bug, or to consider a feature request. In most cases the support team can create these issues on your behalf and assign the correct labels. Sometimes we ask the customer to create these issues when they might have more knowledge of the issue or the ability to convey the requirements more clearly. Once the issue is created on it is up to the product managers and engineering managers to prioritize and drive the fix or feature to completion. The support team can only advocate on behalf of customers to reconsider a priority. Our involvement from this point on is more minimal.

See also: Issue Creation

Outside of the Scope of Support for Self-managed Instances

Out of Scope Example What's in-scope then?
3rd party applications and integrations I can't get Jenkins to run builds kicked off by GitLab. Please help me figure out what is going on with my Jenkins server. GitLab Support can help ensure that GitLab is providing properly formatted data to 3rd party applications and integrations.
Debugging EFS problems GitLab is slow in my HA setup. I'm using EFS. EFS is not recommended for HA setups (see our HA on AWS doc).

GitLab Support can help verify that your HA setup is working as intended, but will not be able to investigate EFS backend storage issues.
Troubleshooting non-GitLab Omnibus components I'm trying to get GitLab to work with Apache, can you provide some pointers? GitLab Support will only assist with the specific components and versions that ship with the GitLab Omnibus package, and only when used as a part of a GitLab installation.
Local modifications to GitLab We added a button to ring a bell in our office any time an MR was accepted, but now users can't log in. GitLab Support would direct you to create a feature request or submit a merge request for code review to incorporate your changes into the GitLab core.
Old versions of GitLab I'm running GitLab 7.0 and X is broken. GitLab Support will invite you to upgrade your installation to a more current release. Only the current and two previous major versions are supported.

Please also review the items outlined in the Outside of the Scope of Support for all tiers section.