kotovalexarian-likes-gitlab/gitlab-org--gitlab-foss
1
0
Fork 0
Code Releases Activity

Documenting that resolved JIRA tickets are not automatically transitioned

Browse source
This commit is contained in:
Edouard 2017-12-29 11:09:49 +00:00
parent eb400b5e02
commit c630bced67
1 changed files with 5 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
doc/user/project/integrations/jira.md
View file

@ -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 - 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 close an issue in Jira. You can change your projects default branch under
[project settings](img/jira_project_settings.png). [project settings](img/jira_project_settings.png).
- The JIRA issue will not be transitionned if it has a resolution.
### JIRA issue closing example ### 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 Make sure the `Transition ID` you set within the JIRA settings matches the one
your project needs to close a ticket. 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 [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-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 [jira]: https://www.atlassian.com/software/jira