...
The features below allow a user to take a helicopter and detailed views on commits, branches and pull requests which were created for release or version.
| Noteinfo |
|---|
The features will be only available if a Jira instance is integrated with Bitbucket or GitHub instances, GitHub (Hosted and Enterprise) and GitLab (Cloud and OnPrem). Otherwise, no data will be presented. Please read details about the integration of Jira with Bitbucket or and GitHub here: https://confluence.atlassian.com/bitbucketserver/linking-bitbucket-server-with-jira-776640408.html GitLab (OnPrem) will require some additional configuration please navigate to Annex A at the bottom of the page. |
Code view
Code view could be enabled from the Issues tab on release or version details screen.
...
User can navigate to the repository to see the commit details and changes in particular files.
...
Annex A: GitLab (OnPrem) integration
There’s no official integration between Jira and GitLab (OnPrem) at the moment. Good news there are some unofficial work around for DVCS account to work out of the box.
...
Please follow the steps below:
You need to upgrade GitLab version to 13.4.3. (We tested on: GitLab Community Edition 13.4.3)
Configure connector from GitLab side
.png?version=1&modificationDate=1608067037560&cacheVersion=1&api=v2)
Navigate to Jira and do the configuration of DVCS account according to the following instructions:
.png?version=1&modificationDate=1608067165287&cacheVersion=1&api=v2)
Click add and receive an error from GitLab side:)
.png?version=3&modificationDate=1608067414411&cacheVersion=1&api=v2)
Amend the URL which was used for redirect to GitLab:
.png?version=1&modificationDate=1608067797712&cacheVersion=1&api=v2)
Replace repo to api as showed below and press Enter
As result, the configuration will be completed
.png?version=1&modificationDate=1608067559870&cacheVersion=1&api=v2)
Please leave a ticket with our support team if you have any difficulties with this work around and we would be happy to advice.