Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
Tatuya Kamada
gitlab-ce
Commits
07dc5170
Commit
07dc5170
authored
Apr 26, 2015
by
Stan Hu
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Improve documentation of configuring external issue trackers
Closes #1514
parent
16db51ec
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
5 additions
and
0 deletions
+5
-0
doc/integration/external-issue-tracker.md
doc/integration/external-issue-tracker.md
+5
-0
No files found.
doc/integration/external-issue-tracker.md
View file @
07dc5170
...
...
@@ -36,4 +36,9 @@ In GitLab Admin section, navigate to `Service Templates` and choose the service
After the template is created, the template details will be pre-filled on the project service page.
NOTE: 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 depecated, and all issue tracker URLs must be configured directly
within the project's Services settings.
Support to add your commits to the Jira ticket automatically is
[
available in GitLab EE
](
http://doc.gitlab.com/ee/integration/jira.html
)
.
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment