2014-04-24 18:48:22 -04:00
# External issue tracker
2016-01-08 06:43:33 -05:00
GitLab has a great issue tracker but you can also use an external one such as
2016-06-26 13:36:43 -04:00
Jira, Redmine, or Bugzilla. Issue trackers are configurable per GitLab project and allow
2016-01-08 06:43:33 -05:00
you to do the following:
2014-01-24 06:09:33 -05:00
2017-06-30 08:47:53 -04:00
- you can reference these external issues inside GitLab interface
(merge requests, commits, comments) and they will be automatically converted
into links
2015-02-18 23:49:19 -05:00
2017-07-24 02:14:06 -04:00
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-02-12 20:06:55 -05:00
## Configuration
2016-01-08 06:43:33 -05:00
The configuration is done via a project's **Services** .
2015-02-12 20:06:55 -05:00
2016-01-08 06:43:33 -05:00
### Project Service
2015-02-12 20:06:55 -05:00
2016-01-08 06:43:33 -05:00
To enable an external issue tracker you must configure the appropriate **Service** .
Visit the links below for details:
2015-02-12 20:06:55 -05:00
2017-02-03 13:41:35 -05:00
- [Redmine ](../user/project/integrations/redmine.md )
- [Jira ](../user/project/integrations/jira.md )
- [Bugzilla ](../user/project/integrations/bugzilla.md )
2017-11-21 10:21:50 -05:00
- [Custom Issue Tracker ](../user/project/integrations/custom_issue_tracker.md )
2015-02-12 20:06:55 -05:00
### Service Template
2016-01-08 06:43:33 -05:00
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-04-26 19:44:22 -04:00
2017-02-03 13:41:35 -05:00
Read more on [Services Templates ](../user/project/integrations/services_templates.md ).
