summaryrefslogtreecommitdiff
path: root/doc/integration/external-issue-tracker.md
diff options
context:
space:
mode:
authordosire <sytses@gmail.com>2014-01-24 12:09:33 +0100
committerdosire <sytses@gmail.com>2014-01-24 12:09:33 +0100
commit17b422cf97c9f66ac9e87f9e22480042ccb37ce5 (patch)
treead582a608d6131316cf3de577a4e044e9f291847 /doc/integration/external-issue-tracker.md
parent2adbc0b778985ee6b0a78b5acd845904520ccc64 (diff)
downloadgitlab-ce-17b422cf97c9f66ac9e87f9e22480042ccb37ce5.tar.gz
Jira integration documentation.
Diffstat (limited to 'doc/integration/external-issue-tracker.md')
-rw-r--r--doc/integration/external-issue-tracker.md7
1 files changed, 7 insertions, 0 deletions
diff --git a/doc/integration/external-issue-tracker.md b/doc/integration/external-issue-tracker.md
new file mode 100644
index 00000000000..fb645a5c9e6
--- /dev/null
+++ b/doc/integration/external-issue-tracker.md
@@ -0,0 +1,7 @@
+GitLab has a great issue tracker but you can also use an external issue tracker such as JIRA or Redmine. This is something that you can turn on per GitLab project. If for example you configure JIRA it provides the following functionality:
+
+- 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;
+- textual references to PROJECT-1234 in comments, commit messages get turned into HTML links to the corresponding JIRA issue.
+
+Also see the [screenshot](jira-intergration-points.png) below.