2020-07-28 23:09:34 +05:30
|
|
|
# Service templates
|
2017-08-17 22:00:37 +05:30
|
|
|
|
2020-07-28 23:09:34 +05:30
|
|
|
Using a service template, GitLab administrators can provide default values for configuring integrations at the project level.
|
|
|
|
|
|
|
|
|
|
When you enable a service template, the defaults are applied to **all** projects that do not
|
|
|
|
|
already have the integration enabled or do not otherwise have custom values saved.
|
|
|
|
|
The values are pre-filled on each project's configuration page for the applicable integration.
|
|
|
|
|
|
|
|
|
|
If you disable the template, these values no longer appear as defaults, while
|
|
|
|
|
any values already saved for an integration remain unchanged.
|
2017-08-17 22:00:37 +05:30
|
|
|
|
|
|
|
|
## Enable a service template
|
|
|
|
|
|
2020-03-13 15:44:24 +05:30
|
|
|
Navigate to the **Admin Area > Service Templates** and choose the service
|
|
|
|
|
template you wish to create.
|
2017-08-17 22:00:37 +05:30
|
|
|
|
2020-07-28 23:09:34 +05:30
|
|
|
## Service for external issue trackers
|
2017-08-17 22:00:37 +05:30
|
|
|
|
2020-07-28 23:09:34 +05:30
|
|
|
The following image shows an example service template for Redmine.
|
2017-08-17 22:00:37 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
For each project, you will still need to configure the issue tracking
|
|
|
|
|
URLs by replacing `:issues_tracker_id` in the above screenshot with the ID used
|
2020-07-28 23:09:34 +05:30
|
|
|
by your external issue tracker.
|
