2014-09-02 18:07:02 +05:30
# External issue tracker
2016-01-14 18:37:52 +05:30
GitLab has a great issue tracker but you can also use an external one such as
2016-08-24 12:49:21 +05:30
Jira, Redmine, or Bugzilla. Issue trackers are configurable per GitLab project and allow
2016-01-14 18:37:52 +05:30
you to do the following:
2014-09-02 18:07:02 +05:30
2017-08-17 22:00:37 +05:30
- you can reference these external issues inside GitLab interface
(merge requests, commits, comments) and they will be automatically converted
into links
2015-04-26 12:48:37 +05:30
2017-09-10 17:25:29 +05:30
You can have enabled both external and internal GitLab issue trackers in parallel. The **Issues** link always opens the internal issue tracker and in case the internal issue tracker is disabled the link is not visible in the menu.
2015-04-26 12:48:37 +05:30
## Configuration
2016-01-14 18:37:52 +05:30
The configuration is done via a project's **Services** .
2015-04-26 12:48:37 +05:30
2016-01-14 18:37:52 +05:30
### Project Service
2015-04-26 12:48:37 +05:30
2016-01-14 18:37:52 +05:30
To enable an external issue tracker you must configure the appropriate **Service** .
Visit the links below for details:
2015-04-26 12:48:37 +05:30
2017-08-17 22:00:37 +05:30
- [Redmine ](../user/project/integrations/redmine.md )
- [Jira ](../user/project/integrations/jira.md )
- [Bugzilla ](../user/project/integrations/bugzilla.md )
2018-03-17 18:26:18 +05:30
- [Custom Issue Tracker ](../user/project/integrations/custom_issue_tracker.md )
2015-04-26 12:48:37 +05:30
### Service Template
2016-01-14 18:37:52 +05:30
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.
2015-09-11 14:41:01 +05:30
2017-08-17 22:00:37 +05:30
Read more on [Services Templates ](../user/project/integrations/services_templates.md ).
