Integrating JIRA with Code Development Tools

If you connect JIRA to a compatible development tool, JIRA will provide you with a range of functionality and information related to your development work.


These are the features that you will enable, if you connect JIRA to the development tools listed below. We recommend that you use the latest version of each application. If you are not using the latest versions, see the version matrix to find out which features are available.

Development panel on issues

A Development panel is shown on the View Issue screen that provides the following functionality:

  • Bitbucket: view and create branches, view and create pull requests, view commits
  • FishEye/Crucible: view commits, view branches, view and create reviews
  • Bamboo: view the status of builds and deployments
  • GitHub or GitHub Enterprise: view commits, branches and pull requests

For more information about using the Development panel, see Streamlining your development with JIRA.


Making it work

Connecting Bitbucket, GitHub or GitHub Enterprise to JIRA

Connections to Bitbucket, GitHub and GitHub Enterprise are done via the DVCS connector add-on that is bundled with JIRA.

Connecting Bitbucket Server, FishEye, Crucible or Bamboo to JIRA

Connections to Bitbucket Server, FishEye/Crucible and Bamboo use application links.

  • When you create a new application link between JIRA and an instance of Bitbucket Server, FishEye, Crucible or Bamboo, 2-legged (2LO) and 3-legged OAuth (3LO) are enabled by default. 2LO is required for information from any of those applications to be included in the summaries in the Development panel; 3LO checks that a user has authenticated with the other applications before they get to see the information in any of the details dialogs. 

  • If you are upgrading from existing instances of JIRA, Bitbucket Server, FishEye, Crucible or Bamboo:
    You may need to reconfigure the application link(s) between JIRA and the other applications. To enable the integration features, each application link must use 2-legged OAuth for both incoming and outgoing authentication. 

    1. Choose > Add-ons. Select Application Links in the left menu.
    2. Choose Edit for the application link.
    3. On the Outgoing Authentication tab, click OAuth. Ensure that Allow 2-legged OAuth is checked. Repeat for the Incoming Authentication tab. The application link update process will involve logging you into the other application for a short time to configure that end of the link, before returning you to JIRA.

Connecting other code development tools to JIRA

You can connect tools to JIRA, other than the ones listed on the version matrix. These tools do not enable the same integration features, but connecting them to JIRA does enable other functionality. See the pages below for instructions on how to connect these applications to JIRA and information about the functionality that is enabled.

If your other applications are running on the same machine as JIRA (already installed), you need to ensure that the URL paths are different for the applications and JIRA. This will differentiate the applications and avoid authentication/session issues with OAuth and Application Links. For example, if you were running FishEye and JIRA, you would change the default paths to:

https://localhost:8060/fisheye (rather than http://localhost:8060/)

This can be done for FishEye/Crucilbe as follows:

  1. Edit the config.xml in your FishEye/Crucible data directory.
  2. Add the context attribute to the web-server  element:
<web-server context="/fisheye">


Was this helpful?

Thanks for your feedback!

Why was this unhelpful?

Have a question about this article?

See questions about this article

Powered by Confluence and Scroll Viewport