Viewing the Code Development Information for an Issue
If your administrator has connected JIRA to a compatible development tool, a Development panel will be displayed on the View Issue screen. Depending on which tools JIRA is connected to, the Development panel provides the following functionality:
- Bitbucket or Bitbucket Server: view and create branches, view commits, view and create pull requests
- FishEye/Crucible(Git/Subversion/Perforce/CVS): view branches (not create), view commits, view and create reviews
- Bamboo: view the status of builds and deployments
- GitHub or GitHub Enterprise: view branches (not create), view commits, view and create pull requests
Starting in JIRA 6.2.2 the Source and Reviews tabs are only displayed if JIRA is unable to display the associated information in the Development Tools panel.
Before you begin
- Your JIRA administrator needs to have set up JIRA and your development tools correctly. Refer your administrator to Integrating JIRA with Code Development Tools.
- You must have the 'view development tools' permission to be able to see the Development panel.
Make your development information available in JIRA
You must tag information in your code/development tool appropriately, if you want it to be made available in JIRA (e.g. display as a link in the Development panel).
Commits: Include the issue key* in the commit message.
Branches: Include the issue key* in the branch name.
Pull requests: Include the issue key* in the pull request's title or in the source branch name.
Reviews: Include the issue key* in the title of the review.
Builds: A build is automatically linked to a JIRA issue if a commit involved in the build has the JIRA issue key in its commit message.
Deployments: A deployment is linked to a JIRA issue if a commit involved in the deploy has the issue key in its commit message.
* Note, the JIRA issue key must conform to the default JIRA key format, that is, two or more uppercase letters ([A-Z][A-Z]+), followed by a hyphen and the issue number, for example EG-123.
View the Development panel
If everything has been set up correctly, you will see a Development panel on each of your issues, similar to the screenshot below. The Development panel provides you with just enough information to evaluate the status of an issue's development, at a glance.
Notes:
The build(s) status in the Development panel is:
if all the different builds (for example, unit tests, functional tests, deploy to staging) have passed.
if at least one run failed for any build by any linked build server.
Investigate and action the information
If you want to investigate something on the the Development panel, you can click the item to display a dialog with more details. The dialog provides links for you to action or drill into. Note, you may be prompted to authenticate with the linked application first.
For example, say that the development panel was showing this: 3 builds . You could click 3 builds to open a dialog showing which of the three builds are failing. If you wanted to investigate further, then you could click the build plan or build result to view it in Bamboo.
Here are the actions you can do, via the Development panel:
BITBUCKET FISHEYE GITHUB
Click n branches in the Development panel to open a dialog in JIRA that shows the branches for the linked SCM. If JIRA has been linked to more than one SCM, a tab will show for each SCM product (e.g. Bitbucket Server). The branches will be grouped under each SCM in these tabs.
- Click a repository or branch to open the linked SCM at the relevant repository/branch.
- Hover over a Pull request status (e.g. MERGED) to show a popup displaying a link to the pull request.
- Click Create pull request to create a pull request for the branch (to merge it back to master).
BITBUCKET FISHEYE GITHUB
Click n commits in the Development panel to open a dialog in JIRA that shows the commits and related files for the linked SCM. If JIRA has been linked to more than one SCM, a tab will show for each SCM product (e.g. Bitbucket Server). The commits will be grouped under each SCM in these tabs. If a commit is greyed out, it has been merged through a pull request.
- Click a repository or commit to open the SCM at the relevant repository/branch.
- If JIRA is linked to more than one SCM, the dialog may show duplicate commits across tabs. For example, you may have pointed FishEye and Bitbucket Server to the same repository.
- (Bitbucket only) If the commits belong to a fork of a repository, they will be grouped under the fork. The fork will also have a link to the original repository, "Fork of <repository name>" .
BITBUCKET GITHUB
Click n pull requests in the Development panel to open a dialog on JIRA that shows the pull requests for the linked SCM(s). If JIRA has been linked to more than one SCM, a tab will show for each SCM product (e.g. Bitbucket Server). The pull requests will be grouped under each SCM in these tabs.
- Click a pull request to open it in the linked SCM.
- Hover over a user icon to show the user's name.
CRUCIBLE
Click n reviews in the Development panel to open a dialog on JIRA that shows the reviews.
- Click a review to open it in Crucible.
BAMBOO
Click n builds in the Development panel to open a dialog on JIRA that shows the builds.
- Click a plan or build result to view it in Bamboo.
BAMBOO
Click Deployed (to environment) in the Development panel to open a dialog on JIRA that shows the deployment .
- Click an environment or release to view it in Bamboo.
Putting it all together
Want to know how this information can help your development team do their work better? Check out the following guide: