diff options
author | Matt Lee <mattl@gitlab.com> | 2017-01-23 11:09:02 -0500 |
---|---|---|
committer | Matt Lee <mattl@gitlab.com> | 2017-01-23 11:09:02 -0500 |
commit | 87e088bd9292dc1efbeafe4cbdadb96a8f497eb7 (patch) | |
tree | a5e863137b3e10ea235ba824e199b21f5a18ff88 | |
parent | 6c65f7a7ce52fadcf53ea2395103de32b0107874 (diff) | |
download | gitlab-ce-27091-doc-fix.tar.gz |
WIP: Update documentation broken links27091-doc-fix
-rw-r--r-- | doc/project_services/jira.md | 4 | ||||
-rw-r--r-- | doc/project_services/kubernetes.md | 2 |
2 files changed, 3 insertions, 3 deletions
diff --git a/doc/project_services/jira.md b/doc/project_services/jira.md index 390066c9989..80e453a91f4 100644 --- a/doc/project_services/jira.md +++ b/doc/project_services/jira.md @@ -6,7 +6,7 @@ user name and password. Connecting to a JIRA server via CAS is not possible. Each project can be configured to connect to a different JIRA instance, see the [configuration](#configuration) section. If you have one JIRA instance you can pre-fill the settings page with a default template. To configure the template -see the [Services Templates][services-templates] document. +see the [Services Templates][services_templates] document. Once the project is connected to JIRA, you can reference and close the issues in JIRA directly from GitLab. @@ -204,5 +204,5 @@ JIRA issue references and update comments will not work if the GitLab issue trac Make sure the `Transition ID` you set within the JIRA settings matches the one your project needs to close a ticket. -[services-templates]: ../project_services/services_templates.md +[services_templates]: ../project_services/services_templates.md [jira-repo-docs]: https://gitlab.com/gitlab-org/gitlab-ce/blob/8-13-stable/doc/project_services/jira.md diff --git a/doc/project_services/kubernetes.md b/doc/project_services/kubernetes.md index 59d5da702f8..99aa9e44bdb 100644 --- a/doc/project_services/kubernetes.md +++ b/doc/project_services/kubernetes.md @@ -8,7 +8,7 @@ the [configuration](#configuration) section. If you have a single cluster that you want to use for all your projects, you can pre-fill the settings page with a default template. To configure the -template, see the [Services Templates](services-templates.md) document. +template, see the [Services Templates](services_templates.md) document. ## Configuration |