Commit b39d76ba authored by Victor Wu's avatar Victor Wu

Jira dev panel docs merge requests

parent c4248e7c
...@@ -82,13 +82,16 @@ Specify the GitLab group name accordingly. (Note that you can also specify GitLa ...@@ -82,13 +82,16 @@ Specify the GitLab group name accordingly. (Note that you can also specify GitLa
are really GitLab "groups" behind the scenes. In that case, all the projects for that user would are really GitLab "groups" behind the scenes. In that case, all the projects for that user would
be made known to JIRA, up to the permissions of the user setting up the integration.) be made known to JIRA, up to the permissions of the user setting up the integration.)
You can now see the linked `branches` and `commits` when entering a JIRA issue. You can now see the linked `branches`, `commits`, and `merge requests` when entering a JIRA issue.
(Inside the Jira issue, merge requests will be called "pull requests").
![Branch and Commit links on JIRA issue](img/jira_dev_panel_jira_setup_3.png) ![Branch, Commit and Pull Requests links on JIRA issue](img/jira_dev_panel_jira_setup_3.png)
Click these links to see your GitLab repository data. Click the links to see your GitLab repository data.
![GitLab commit details on a JIRA issue](img/jira_dev_panel_jira_setup_4.png) ![GitLab commits details on a JIRA issue](img/jira_dev_panel_jira_setup_4.png)
![GitLab merge requests details on a JIRA issue](img/jira_dev_panel_jira_setup_5.png)
## Limitations ## Limitations
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment