Configuring development tools

On this page

Still need help?

The Atlassian Community is here for you.

Ask the community

Jira Software can be connected to a range of development tools to help keep your project tracking in sync with your development work. By connecting Jira Software to development tools, you can:

  • Connect to repository managers, like Bitbucket or GitHub, where you can further:
    • configure issues to automatically transition when certain events occur in your repository, such as commits and branches created, pull requests merged and declined, and more
    • create branches directly from issues in Jira Software
    • see every issue with its related commits, branches, and pull requests in Jira Software
  • Connect to Crucible for code reviews, where you can further:
    • configure issues to automatically transition when a review changes status
    • see every issue with its related reviews in Jira Software
  • Connect to Bamboo, and you can see every issue with its related builds and deployments in Jira Software.

On this page:

Connecting Jira Software to your development tools

Make sure that you have the right permissions. You need to be a Jira administrator to connect Jira Software to another application. You also need to be an administrator for your development tool.

Follow the instructions on Integrating with development tools (

Jira admin

 documentation) to connect Jira Software to your development tools.

Configuring Jira Software and your development tools

Some features will be automatically enabled when you connect Jira Software to your development tools. Others require some additional configuration. Each feature is listed below, including the configuration work required to set it up.

Development panel on issues

The Development panel is shown on every issue, and helps you to evaluate the development status of an issue at a glance. If you need to investigate further, click any item to display more details, or drill down into the development tool.

You don't need to do any further configuration once you have connected Jira Software to your development tools. However, your team will need to know how to reference issues in their development work.

Learn more: Referencing issues in your development work

We're gradually rolling out a new issue view, which you may see on your boards and in your backlog. The issue detail view will look a little different and some procedures will change slightly. Take a look at our info page to see what's changed and get the latest updates.

View issue information in your developer tools

If you have connected Jira Software to one of the supported developer tools, like Bitbucket, Bamboo, Fisheye/Crucible, you will be able to view information about the issues in those tools. For example, in Bitbucket, you'll be able to see the issues that were referenced in a changeset; in Bamboo, you'll be able to see the issues linked to a plan's builds.

Here's an example of an issue key (MSP-15) in a commit message in Bitbucket:

When you click the issue key in Bitbucket, you'll see the issue view:

Learn more: Bitbucket ServerBitbucket CloudBambooFisheye, Crucible

Create a branch from an issue

If you use Bitbucket Cloud or Bitbucket Server to manage your code repositories, you can create code branches directly from issues in Jira Software via the Create branch link. The link will open your connected repository application and launch the process of creating a branch for you. If you have multiple applications connected, then you can choose where you'd like to create the branch.

Workflow triggers

You can configure triggers in workflows that respond to events in your linked development tools. This helps your team keep their issue statuses in sync with their development work, rather than lagging behind. For example, when a developer creates a branch in Bitbucket to start work on an issue, they can reference the issue in the branch name, and the issue will automatically be transitioned from 'Open' to 'In progress'.

You'll need to add triggers to your workflow(s) after connecting Jira Software to your development tools. We recommend that you read our guide on configuring workflow triggers.

Learn more: Configuring workflow triggers (

Jira admin

 documentation)

Development information in the Release Hub

The Release Hub on your board lets you see the progress of your release (of a version) and determine what is likely to ship, at a glance. You can see all of the issues in the version, broken down by status category, as well as problems that could affect the release of the version (e.g. issues that should be in the release but are part of unmerged pulled requests, issues that haven't had code reviews, broken builds, etc).

You don't need to do any further configuration once you have connected Jira Software to your development tools. However, your team will need to know how to reference issues in their development work.

Learn more: Referencing issues in your development work

Next steps

 Need help? If you can't find the answer you need in our documentation, we have other resources available to help you. See Getting help.

Last modified on Apr 4, 2018

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.