summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorEdouard <edouard@gomez-vaez.com>2017-12-29 11:09:49 +0000
committerEdouard <edouard@gomez-vaez.com>2017-12-29 11:09:49 +0000
commitc630bced675a30cff568ccc2c0eb71ef0e61651a (patch)
treecc70b4beb46c6d2b37788d13a4641d1945e82a1c
parenteb400b5e029ce35c516056043560ab880276334f (diff)
downloadgitlab-ce-c630bced675a30cff568ccc2c0eb71ef0e61651a.tar.gz
Documenting that resolved JIRA tickets are not automatically transitioned
-rw-r--r--doc/user/project/integrations/jira.md5
1 files changed, 5 insertions, 0 deletions
diff --git a/doc/user/project/integrations/jira.md b/doc/user/project/integrations/jira.md
index 7dc234a9759..411547e9800 100644
--- a/doc/user/project/integrations/jira.md
+++ b/doc/user/project/integrations/jira.md
@@ -173,6 +173,7 @@ where `PROJECT-1` is the issue ID of the JIRA project.
- Only commits and merges into the project's default branch (usually **master**) will
close an issue in Jira. You can change your projects default branch under
[project settings](img/jira_project_settings.png).
+- The JIRA issue will not be transitionned if it has a resolution.
### JIRA issue closing example
@@ -222,6 +223,10 @@ 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.
+Make sure that the JIRA issue is not already marked as resolved, in other word that
+the JIRA issue resolution field is not set. (It should not be striked through in
+JIRA lists).
+
[services-templates]: services_templates.md
[jira-repo-old-docs]: https://gitlab.com/gitlab-org/gitlab-ce/blob/8-13-stable/doc/project_services/jira.md
[jira]: https://www.atlassian.com/software/jira