2017-02-16 08:05:51 -05:00
|
|
|
# Services templates
|
2017-02-03 13:41:35 -05:00
|
|
|
|
|
|
|
|
A GitLab administrator can add a service template that sets a default for each
|
2017-02-16 08:05:51 -05:00
|
|
|
project. After a service template is enabled, it will be applied to new
|
|
|
|
|
projects only and its details will be pre-filled on the project's Service page.
|
2017-02-03 13:41:35 -05:00
|
|
|
|
2017-02-16 08:05:51 -05:00
|
|
|
## Enable a service template
|
2017-02-03 13:41:35 -05:00
|
|
|
|
|
|
|
|
In GitLab's Admin area, navigate to **Service Templates** and choose the
|
|
|
|
|
service template you wish to create.
|
|
|
|
|
|
2017-02-16 08:05:51 -05:00
|
|
|
## Services for external issue trackers
|
|
|
|
|
|
|
|
|
|
In the image below you can see how a service template for Redmine would look
|
|
|
|
|
like.
|
2017-02-03 13:41:35 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
---
|
|
|
|
|
|
2017-02-16 08:05:51 -05:00
|
|
|
For each project, you will still need to configure the issue tracking
|
2017-02-03 13:41:35 -05:00
|
|
|
URLs by replacing `:issues_tracker_id` in the above screenshot with the ID used
|
|
|
|
|
by your external issue tracker. Prior to GitLab v7.8, this ID was configured in
|
|
|
|
|
the project settings, and GitLab would automatically update the URL configured
|
|
|
|
|
in `gitlab.yml`. This behavior is now deprecated and all issue tracker URLs
|
2017-02-16 08:05:51 -05:00
|
|
|
must be configured directly within the project's **Integrations** settings.
|
