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
Kazuhiko Shiozaki
gitlab-ce
Commits
c53aad31
Commit
c53aad31
authored
Jan 25, 2016
by
Achilleas Pipinellis
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Add proper screenshot and comment on the output
[ci skip]
parent
6c46b79d
Changes
3
Hide whitespace changes
Inline
Side-by-side
Showing
3 changed files
with
14 additions
and
5 deletions
+14
-5
doc/project_services/img/jira_issue_closed.png
doc/project_services/img/jira_issue_closed.png
+0
-0
doc/project_services/img/jira_issues_workflow.png
doc/project_services/img/jira_issues_workflow.png
+0
-0
doc/project_services/jira.md
doc/project_services/jira.md
+14
-5
No files found.
doc/project_services/img/jira_issue_closed.png
0 → 100644
View file @
c53aad31
90.4 KB
doc/project_services/img/jira_issues_workflow.png
View replaced file @
6c46b79d
View file @
c53aad31
102 KB
|
W:
|
H:
103 KB
|
W:
|
H:
2-up
Swipe
Onion skin
doc/project_services/jira.md
View file @
c53aad31
...
...
@@ -167,9 +167,10 @@ Where:
### Closing JIRA issues
JIRA issues can be closed directly from GitLab by using trigger words in
commits and merge requests. When a commit, which contains the trigger word
followed by the JIRA issue ID in the commit message, is pushed, GitLab will
add a comment in the mentioned JIRA issue and immediately close it.
commits and merge requests. When a commit which contains the trigger word
followed by the JIRA issue ID in the commit message is pushed, GitLab will
add a comment in the mentioned JIRA issue and immediately close it (provided
the transition ID was set up correctly).
There are currently three trigger words, and you can use either one to achieve
the same goal:
...
...
@@ -187,7 +188,7 @@ in GitLab. The workflow would be something like this:
1.
Create a new branch
1.
Fix the bug
1.
Commit the changes and push b
ack
to GitLab
1.
Commit the changes and push b
ranch
to GitLab
1.
Open a new merge request and reference the JIRA issue including one of the
trigger words, e.g.:
`Fixes GITLAB-1`
, in the description
1.
Submit the merge request
...
...
@@ -207,9 +208,17 @@ issue look like.
Once this merge request is merged, the JIRA issue will be automatically closed
with a link to the commit that resolved the issue.
![
The GitLab integration user leaves a comment on JIRA
](
img/jira_
service_close_issue
.png
)
![
The GitLab integration user leaves a comment on JIRA
](
img/jira_
issue_closed
.png
)
---
You can see from the above image that there are four references to GitLab:
-
The first is from a comment in a specific commit
-
The second one is from the JIRA issue reference in the merge request
description
-
The third is from the actual commit that solved the issue
-
And the fourth one is from the commit that the merge request created
[
services-templates
]:
../project_services/services_templates.md
"Services templates documentation"
[
JIRA Core
]:
https://www.atlassian.com/software/jira/core
"The JIRA Core website"
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