Integrating with development tools using app links
Using app links is one of the integration options for development tools that lets you link your Bitbucket Server, Bamboo, and Fisheye / Crucible instances to Jira. Once linked, you can view the development information in your Jira issues. Learn more about integrating with development tools
Here’s a list of dev tools that you can integrate, and their supported versions:
|Bitbucket Server||Fisheye / Crucible||Bamboo|
|Bitbucket Server 4.0+ (Stash 2.10)||3.3+/3.3+||5.4+|
If you’re using other development tools that aren’t listed here, like Bitbucket Cloud or GitHub, you can integrate them using DVCS.
Integrating your development tools
To integrate your development tools:
In Jira, go to Administration > Applications > Application links.
Enter the application URL you want to link.
For more info on using app links, see Using app links to link to other applications.
If your developer tools instances are running on the same machine as Jira Software, you'll need to ensure that the applications uses distinct web contexts. This avoids authentication and session issues with OAuth and application links. For example, if you were running Fisheye and Jira, you would change the default paths to:
Here are a few of our development tools integrated through app links:
Here’s what happens after adding your account:
Syncing information: Your development tools appear on the Application links page and Jira starts syncing them.
Matching issues: If your commits and pull requests include issue keys, Jira will try to find them and add the relevant information to your issues. For details, see Referencing issues in your development work.
Displaying dev info: If referenced correctly, the dev information will be added to your issues to give everyone involved more context. For details, see Viewing the dev info for an issue.
Workflow triggers: One of the benefits of integrating your development tools is adding workflow triggers that, for example, lets you change the issue status after you create a new branch. For details, see Configuring workflow triggers.