External issue tracker
GitLab has a great issue tracker but you can also use an external one such as Jira, Redmine, YouTrack, or Bugzilla. External issue trackers are configurable per GitLab project.
Once configured, you can reference external issues using the format CODE-123, where:
-
CODEis a unique code for the tracker. -
123is the issue number in the tracker.
These references in GitLab merge requests, commits, or comments are automatically converted to links to the issues.
You can keep GitLab’s issue tracker enabled in parallel or disable it. When enabled, the Issues link in the GitLab menu always opens the internal issue tracker. When disabled, the link is not visible in the menu.
Configuration
The configuration is done via a project’s Services.
Project Service
To enable an external issue tracker you must configure the appropriate Service. Visit the links below for details:
Service Template
To save you the hassle from configuring each project’s service individually, GitLab provides the ability to set Service Templates which can then be overridden in each project’s settings.
Read more on Services Templates.
Help and feedback
If there's something you don't like about this feature
To propose functionality that GitLab does not yet offer
To further help GitLab in shaping new features
If you didn't find what you were looking for
If you want help with something very specific to your use case, and can use some community support
POST ON GITLAB FORUM
If you have problems setting up or using this feature (depending on your GitLab subscription)
REQUEST SUPPORT
To view all GitLab tiers and features or to upgrade
If you want to try all features available in GitLab.com
If you want to try all features available in GitLab self-managed
If you spot an error or a need for improvement and would like to fix it yourself in a merge request
EDIT THIS PAGE
If you would like to suggest an improvement to this doc