diff options
| author | Marin Jankovski <maxlazio@gmail.com> | 2015-02-13 08:56:25 -0800 |
|---|---|---|
| committer | Marin Jankovski <maxlazio@gmail.com> | 2015-02-13 08:56:25 -0800 |
| commit | 01c6806f804d9b76042229e11077190975eb8bf0 (patch) | |
| tree | fcca00d1c707e441c182654a6a842098f962c962 /doc/integration/external-issue-tracker.md | |
| parent | eccf695640680050127c830887631d241dc7c8be (diff) | |
| download | gitlab-ce-01c6806f804d9b76042229e11077190975eb8bf0.tar.gz | |
Text changes recommended by Job.
Diffstat (limited to 'doc/integration/external-issue-tracker.md')
| -rw-r--r-- | doc/integration/external-issue-tracker.md | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/doc/integration/external-issue-tracker.md b/doc/integration/external-issue-tracker.md index a4f67daa563..53d6898b6e8 100644 --- a/doc/integration/external-issue-tracker.md +++ b/doc/integration/external-issue-tracker.md @@ -1,6 +1,6 @@ # External issue tracker -GitLab has a great issue tracker but you can also use an external issue tracker such as Jira, Bugzilla or Redmine. This is something that you can turn on per GitLab project. If for example you configure Jira it provides the following functionality: +GitLab has a great issue tracker but you can also use an external issue tracker such as Jira, Bugzilla or Redmine. You can configure issue trackers per GitLab project. For instance, if you configure Jira it allows you to do the following: - the 'Issues' link on the GitLab project pages takes you to the appropriate Jira issue index; - clicking 'New issue' on the project dashboard creates a new Jira issue; @@ -12,7 +12,7 @@ GitLab has a great issue tracker but you can also use an external issue tracker ### Project Service -External issue tracker can be enabled per project basis. As an example, we will configure `Redmine` for project named gitlab-ci. +You can enable an external issue tracker per project. As an example, we will configure `Redmine` for project named gitlab-ci. Fill in the required details on the page: @@ -20,14 +20,14 @@ Fill in the required details on the page: * `description` A name for the issue tracker (to differentiate between instances, for example). * `project_url` The URL to the project in Redmine which is being linked to this GitLab project. -* `issues_url` The URL to the issue in Redmine project that is linked to this GitLab project. Note that the `issues_url` requires `:id` in the url. This id GitLab uses as a placeholder to replace the issue number. +* `issues_url` The URL to the issue in Redmine project that is linked to this GitLab project. Note that the `issues_url` requires `:id` in the url. This id is used by GitLab as a placeholder to replace the issue number. * `new_issue_url` This is the URL to create a new issue in Redmine for the project linked to this GitLab project. ### Service Template -Since external issue tracker needs some project specific details, it is required to enable issue tracker per project level. -GitLab makes this easier by allowing admin to add a service template which will allow GitLab project user with permissions to edit details for its project. +It is necessary to configure the external issue tracker per project, because project specific details are needed for the integration with GitLab. +The admin can add a service template that sets a default for each project. This makes it much easier to configure individual projects. In GitLab Admin section, navigate to `Service Templates` and choose the service template you want to create: |