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
|
|
|
|
|
Jira or Redmine. Issue trackers are configurable per GitLab project and allow
|
|
|
|
|
you to do the following:
|
2014-09-02 18:07:02 +05:30
|
|
|
|
2016-01-14 18:37:52 +05:30
|
|
|
- the **Issues** link on the GitLab project pages takes you to the appropriate
|
|
|
|
|
issue index of the external tracker
|
|
|
|
|
- clicking **New issue** on the project dashboard creates a new issue on the
|
|
|
|
|
external tracker
|
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
|
|
|
|
2016-01-14 18:37:52 +05:30
|
|
|
- [Redmine](../project_services/redmine.md)
|
2016-04-02 18:10:28 +05:30
|
|
|
- [Jira](../project_services/jira.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
|
|
|
|
2016-01-14 18:37:52 +05:30
|
|
|
Read more on [Services Templates](../project_services/services_templates.md).
|
