summaryrefslogtreecommitdiff
path: root/doc/project_services
diff options
context:
space:
mode:
authorAchilleas Pipinellis <axilleas@axilleas.me>2016-02-08 00:37:45 +0200
committerAchilleas Pipinellis <axilleas@axilleas.me>2016-02-08 00:37:45 +0200
commited093f1ef0a75cd6d4b292f94ae11383f0afd9d6 (patch)
tree0a7aeff714bcdb8797d078729594359e38950f44 /doc/project_services
parent7f5a87f12d3a304bbddd0408e15c16abd4bb495e (diff)
downloadgitlab-ce-ed093f1ef0a75cd6d4b292f94ae11383f0afd9d6.tar.gz
Clarify when JIRA service was backported to CE
[ci skip]
Diffstat (limited to 'doc/project_services')
-rw-r--r--doc/project_services/jira.md9
1 files changed, 9 insertions, 0 deletions
diff --git a/doc/project_services/jira.md b/doc/project_services/jira.md
index d6b2e7f521b..7c12557a321 100644
--- a/doc/project_services/jira.md
+++ b/doc/project_services/jira.md
@@ -1,5 +1,12 @@
# GitLab JIRA integration
+_**Note:**
+Full JIRA integration was previously exclusive to GitLab Enterprise Edition.
+With [GitLab 8.3 forward][8_3_post], this feature in now [backported][jira-ce]
+to GitLab Community Edition as well._
+
+---
+
GitLab can be configured to interact with [JIRA Core] either using an
on-premises instance or the SaaS solution that Atlassian offers. Configuration
happens via username and password on a per-project basis. Connecting to a JIRA
@@ -210,3 +217,5 @@ You can see from the above image that there are four references to GitLab:
[services-templates]: ../project_services/services_templates.md "Services templates documentation"
[JIRA Core]: https://www.atlassian.com/software/jira/core "The JIRA Core website"
+[jira-ce]: https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/2146 "MR - Backport JIRA service"
+[8_3_post]: https://about.gitlab.com/2015/12/22/gitlab-8-3-released/ "GitLab 8.3 release post"