2014-09-02 18:07:02 +05:30
|
|
|
# External issue tracker
|
|
|
|
|
|
2019-07-07 11:18:12 +05:30
|
|
|
GitLab has a great [issue tracker](../user/project/issues/index.md) but you can also use an external one
|
|
|
|
|
such as Jira, Redmine, YouTrack, or Bugzilla. External issue trackers are configurable per GitLab project.
|
2014-09-02 18:07:02 +05:30
|
|
|
|
2019-07-07 11:18:12 +05:30
|
|
|
Once configured, you can reference external issues using the format `CODE-123`, where:
|
2015-04-26 12:48:37 +05:30
|
|
|
|
2019-07-07 11:18:12 +05:30
|
|
|
- `CODE` is a unique code for the tracker.
|
|
|
|
|
- `123` is 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.
|
2017-09-10 17:25:29 +05:30
|
|
|
|
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)
|
2019-07-07 11:18:12 +05:30
|
|
|
- [YouTrack](../user/project/integrations/youtrack.md)
|
2017-08-17 22:00:37 +05:30
|
|
|
- [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).
|
