summaryrefslogtreecommitdiff
path: root/doc/user/project/integrations/services_templates.md
diff options
context:
space:
mode:
Diffstat (limited to 'doc/user/project/integrations/services_templates.md')
-rw-r--r--doc/user/project/integrations/services_templates.md26
1 files changed, 26 insertions, 0 deletions
diff --git a/doc/user/project/integrations/services_templates.md b/doc/user/project/integrations/services_templates.md
new file mode 100644
index 00000000000..5b04d7d88b8
--- /dev/null
+++ b/doc/user/project/integrations/services_templates.md
@@ -0,0 +1,26 @@
+# Services templates
+
+A GitLab administrator can add a service template that sets a default for each
+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.
+
+## Enable a service template
+
+In GitLab's Admin area, navigate to **Service Templates** and choose the
+service template you wish to create.
+
+## Services for external issue trackers
+
+In the image below you can see how a service template for Redmine would look
+like.
+
+![Redmine service template](img/services_templates_redmine_example.png)
+
+---
+
+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
+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
+must be configured directly within the project's **Integrations** settings.