Installing Atlassian Tools for Integration with JIRA
The Atlassian development tools work together with JIRA to give your team a fast and guided software development process.
The matrix on this page shows the minimum application versions required to enable the integration features described on Integrating JIRA with Code Development Tools.
|JIRA||FishEye / Crucible||Bamboo||GitHub Enterprise||Bitbucket||Bitbucket Server (formerly Stash)||GitHub||Features enabled|
|6.3.3+ or JIRA Cloud||3.5.2||N/A||11.10.290+||Current||Stash 3.2.0||Current||Workflow triggers|
Development Tools configuration for administrators
The Development Tools section on the project administration screen gives you an overview of the development tools that are connected to your JIRA instance, and of the users who can use the integrations between JIRA and those tools.
The View Permission section lists the user groups that can see the Development panel in a JIRA issue. The Development panel displays the Create Branch link, as well as summary information for your development process, such as the number and status of the related commits, pull requests, reviews and builds. The visibility of the panel is controlled by the "View Development Tools" project permission.
The Applications section lists the development tools that are connected to JIRA, and so shows which applications can take advantage of these integration features.
- In Cloud, any applications that are part of your Cloud subscription are linked together automatically; you don't need to do anything to start using the development tool integration features.
- You can connect your JIRA Cloud to your own locally installed instances of the development tools, such as Bitbucket Server, FishEye or Crucible, by setting up an application link (see below).
- You can connect your JIRA Cloud, or your locally installed instance of JIRA, to Bitbucket, GitHub or GitHub Enterprise using the DVCS Connector in JIRA.
Click Development Tools in the left navigation bar to manage these settings.
Making the integration work
JIRA users only need the "View Development Tools" project permission to be able to see the Development panel. By default, anonymous users (those who are not logged in) don't have this permission, and so do not see the panel.
- A developer simply needs to supply a JIRA issue key, as follows, for the JIRA issue to be automatically linked:
Commits are linked automatically if the issue key is included in the commit message.
Branches are linked automatically if the issue key is included in the branch name.
Pull requests are linked automatically if the issue key is included in the pull request's title or in the source branch name.
Reviews are linked automatically if the issue key is included in the title of the review, or if the issue is linked from the review.
Builds and deployments are linked automatically if a commit involved in the build has the issue key in its commit message.
JIRA must be connected with Bitbucket Server, FishEye, Crucible or Bamboo using a 2-way application link that has both 2-legged and 3-legged authentication enabled. See the Application Links section below.
- JIRA must be connected with Bitbucket, GitHub or GitHub Enterprise using the DVCS Connector in JIRA. See Use the JIRA DVCS Connector.
- When using the supported versions of JIRA and the other applications, the Development panel replaces the Source, Commits and Builds tabs, as well as the Deployment panel, in a JIRA issue. So, for example, you won't see the Source tab, and commits in Bitbucket Server will be accessible from the Development panel. However, if a connected application is older than the supported version, information from that application will continue to be displayed in those locations.
- The details dialogs, for example for commits, may display duplicates, although the number of unique items are reported at the top of the dialog and in the Devlopment panel summary. Duplicate commits, for example, can arise from having both Bitbucket Server and FishEye linked to JIRA, and FishEye in turn connected with Bitbucket Server, so that FishEye indexes, and reports Bitbucket Server commits.
- Users who can see summarized data in the Development panel may not have permission to see in the details dialogs (for example, for branches, commits and pull requests) all the information that contributed to the summaries. That is, the details dialogs respect the access permissions that users have in the connected applications.
- Note that if commits linked to the JIRA issue are involved with a Bamboo build that fails, the first successful build that follows will be reported, even though the original commits are no longer involved with that build.
The DVCS Connector plugin needs to be enabled and configured in JIRA before you'll see information from Bitbucket in the Development panel of a JIRA (or JIRA Agile) issue. See Use the JIRA DVCS Connector Add-on for details. Remember that you won't see Bitbucket information in the Commits tab at the bottom of the JIRA View Issue screen any more.
The Development panel replaces the Builds tab and the Deployments panel in the JIRA View Issue screen.
When FishEye and Crucible (versions 3.3 and later) are linked with JIRA, you'll see FishEye branches and commits, and Crucible reviews, summarized in the Development panel – click on the links to see details of those. You can start the creation of Crucible reviews from the Commits details dialog. Note that with FishEye and Crucible version 3.3 and later, you won't see the Commits and Reviews tabs anymore; however, if any older instances are connected to JIRA, those tabs will continue to be displayed. See Application links below.
When Bitbucket Server (Stash 2.10 or later) is linked with JIRA, you won't see the Source tab at the bottom of the JIRA View Issue screen any more.
The following system plugins are required. These are bundled and enabled by default:
- Atlassian Navigation Links Plugin (com.atlassian.plugins.atlassian-nav-links-plugin)
- Bitbucket Server Dev Summary Plugin (com.atlassian.stash.stash-dev-summary-plugin).
See Application links below.
You can configure the DVCS Connector plugin in JIRA in order to see branch, commits and pull request information in the Development panel of a JIRA issue.
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 an application to be included in the summaries in the Development panel; 3LO requires a user to authenticate with the other application in order to see information in any of the details dialogs.
- Users who can see summarized data in the Development panel may not have permission to see all the information that contributed to those summaries in the details dialogs (for example, for branches, commits and pull requests). That is, the details dialogs respect the access permissions that users have in the connected applications.
- An older application link between JIRA and any of those applications will need to have 2-legged authentication enabled.
An existing application link between JIRA and Bitbucket Server, FishEye, Crucible or Bamboo (that perhaps used Trusted Apps authentication) needs to have 2-legged authentication (2LO) enabled for both outgoing and incoming authentication, so that information from the application can be included in the Development panel summaries.
When updating an older application link to use OAuth, 3-legged authentication is applied by default, but you need to explicitly enable 2LO. Enable 2-legged authentication for the application link from within JIRA as follows:
- Go to the JIRA admin area and click Add-ons > Application Links.
- Click Edit for the app link with the other application.
- For both Outgoing Authentication and Incoming Authentication:
- Click OAuth
- Check Allow 2-legged OAuth.
- Click Update.
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.
Was this helpful?
Thanks for your feedback!