Learn how to set up Jira Software Cloud and integrate it with other products and applications.
Learn how to configure your Jira Software Cloud company-managed projects to suit your agile development processes.
Learn how to create, search, and work with issues in software projects, manage your profile, and more.
Learn how to get started, enable features, and manage and administer team-managed projects.
Plan and view work across multiple teams, projects, and releases with Advanced Roadmaps.
A guide on how to deploy and monitor an application built on AWS using Atlassian and third-party tools.
If your administrator has connected Jira Software to a compatible development tool, a development panel will be displayed on the View Issue screen. Depending on which tools Jira Software is connected to, the development panel provides the following functionalities:
Bamboo: view the status of builds and deployments (Bitbucket pipeline deployments are shown in the release panel)
GitHub or GitHub Enterprise: view branches (not create), view commits, and view and create pull requests
GitLab: view the development information. Learn more about getting started with developer tool integrations and read more about open toolchain.
Before you begin
Your administrator needs to have set up Jira Software and your development tools correctly. Refer your administrator to Integrating with 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 Software
You must reference the issue key in your commit, branch, or pull request if you want it to display as a link in the development panel. For information on how to reference issue keys correctly, see Referencing issues in your development work. Once development information has been linked to an issue, it can’t be removed.
View the development panel
If everything has been set up correctly, you'll 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.
Development panel: Hover over branches, commits, and pull requests to see when they were last updated.
If you have more than 100 cards on the board, we don’t show the development status indicators on the cards.
What does the status lozenge next to the pull requests mean?
The pull request(s) status in the development panel is:
OPEN if there is at least one open pull request.
MERGED if there are no open pull requests, and at least one pull request has been merged.
DECLINED if there are no open or merged pull requests, and at least one pull request has been declined.
What does the status lozenge next to the reviews mean?
The review(s) status in the development panel is:
REVIEW (yellow with black writing) – At least one review in 'Review' status.
APPROVAL (black) – There are no reviews in 'Review' status, and at least one review is in 'Approval' status.
SUMMARIZE (black) – There are no reviews in 'Review' or 'Approval' statuses, and at least one review is in 'Summarize' status.
REJECTED (red) – There are no reviews in 'Review', 'Approval', or 'Summarize' statuses, and at least one review is in 'Rejected' status. (Red)
APPROVAL (green) – All reviews are in 'Closed' status.
'Draft' and 'Abandoned' reviews are not shown.
What does the status lozenge next to the builds mean?
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 in 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, you can click through to see it in your build tool.
Here are the actions you can do via the development panel:
Create feature branches
Click Create branch in the development panel to open your connected SCM, and start the process for creating a branch. If you have multiple applications connected, then you can choose where you'd like to create the branch. The key for the Jira issue will be automatically added to the name of the branch.
See repository branches
BITBUCKET | FISHEYE | GITHUB
Click n branches in the development panel to open a dialog in Jira Software that shows the branches for the linked SCM. If Jira Software has been linked to more than one SCM, a tab will show for each SCM product (For example, Bitbucket). 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 (MERGED, for example) 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).
See commits to repositories
BITBUCKET | FISHEYE | GITHUB
Click n commits in the development panel to open a dialog in Jira Software that shows the commits and related files for the linked SCM. If Jira Software has been linked to more than one SCM, a tab will show for each SCM product (e.g. Bitbucket). 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 Software is linked to more than one SCM, the dialog may show duplicate commits across tabs. For example, you may have pointed Fisheye and Bitbucket 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>".
Create pull requests
BITBUCKET | GITHUB
See the 'See repository branches' section above.
See the status of pull requests
BITBUCKET | GITHUB
Click n pull requests in the development panel to open a dialog on Jira Software that shows the pull requests for the linked SCM(s). If Jira Software has been linked to more than one SCM, a tab will show for each SCM product (e.g. Bitbucket). 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.
See the status of reviews
Click n reviews in the development panel to open a dialog in Jira Software that shows the reviews.
Click a review to open it in Crucible.
See the status of builds
BAMBOO | PIPELINES
Click n builds in the Development panel to open a dialog in Jira Software that shows the builds.
If you need more details, you can click on the links to be taken to your build tool.
See the status of deployments
Click Deployed (to environment) in the development panel to open a dialog in Jira Software that shows the deployment.
Click an environment or release to view it in Bamboo.
Was this helpful?