Overview
The features below allow a user to take a helicopter and detailed views on commits, branches and pull requests which were created for package or version.
The features will be only available if your Jira instance is integrated one of the development tools. Otherwise, no data will be presented.
Please read details about the integration of Jira with
Integrate Jira with development tools
Integrate Jira Cloud with Bitbucket
Integrate with GitHub
Integrate with Bamboo
Integrate with FishEye
Getting started
If your Jira integrated with one of the development tools you can use Code/Commits functionality of Release Management App.
Open any version or package details.
If you open “Issues“ view you will see a “Code“ toggle in the menu ribbon as shown below
Information icon aim to provide initial details and link to this document id you want to read it later again. It also shows a configuration button to proceed with initial Code/Commits functionality configuration
Warning icon is shown if haven't yet configured Code/Commits functionality.
If you open “Commits“ view of the version or package your initial screen will look like the following
By clicking on “Configure“ button in either of the sections you will get a dialog to enter your Atlassian Account email and token. If you do not have one click on the link to generate
This is the only way for Release Management App to connect to development tools integrated with your Jira. We do not use this token for anything else. We also do not store it on our Server (it’s stored in cookies of your browser).
Once you entered your email and token click connect. Upon successful connection all the warnings signs disappear and you can use functionality.
Code view
Code view could be enabled from the Issues tab on release or version details screen.
Enabled code view:
If the Code view enabled the user can’t configure columns anymore. The columns set is predefined.
In the code changes column the user can see:
Number of branches which are created for a particular Jira issue
Quantity of commits
Amount of pull requests and their statuses
In case more than one page of issues lists are available, sorting by Code change column will only work for the current page and will not take data from other pages, in contrast to sorting by any other column in the table.
Such limitation is dictated by technical aspects of code changes data fetching.
After a click at branches, commits or pull requests a user can see a screen with detailed information about each entity:
User can navigate from the details screen to the repository to check the details like changes in the code, code review, etc
Information about builds and environment will not be available in the current version of the release management.
Please create a feature request if you miss this information.
Commits
Commits tab is available on version and release levels.
On the tab, the user can see all commits which belong to version or all versions in the package sorted from newest to oldest.
In order to limit the amount of presented data, commits are presented for the first 1000, recently updated issues in release or version.
In order to receive commits data click “Fetch data“ button. Data loading might take some time. The user will see a data loading progress bar.
User can navigate to the repository to see the commit details and changes in particular files.
e.g.
