Get hands-on training for JIRA Software, Confluence, and more at Atlassian Summit Europe. Register now ›

A few months ago we announced the availability of JIRA Studio, which combines JIRA, Confluence, Subversion, FishEye, and Crucible in a single integrated hosted suite. A big part of what makes JIRA Studio work is Atlassian’s AppLinks, a series of plugins which tie the applications together and allow for a number of new integration points. We’ve now released this plugin for free for our JIRA and Confluence customers – if you’re running a combination of JIRA, Confluence, and/or FishEye/Crucible, please check out the plugins at the links below:
AppLinks documentation
Confluence AppLinks Plugin
JIRA AppLinks Plugin
What does AppLinks give you?
First off, it gives you inter-application hyperlinking with a common link syntax. Once AppLinks is configured, you can type a JIRA issue key (ex. BUG-123) in any Confluence page/comment and it will render as a link once the page/content has been saved – no need to enter the full URL. Along the same lines, referencing a wiki page using format [space key:page] in a JIRA ticket will automatically render it as a link, again with no need to enter the full URL of the Confluence instance. Further, Subversion revisions can also be linked using the same syntax in JIRA and Confluence.
applinksconf.png
Second, and perhaps even more importantly, AppLinks provides ecosystem awareness. This means that because each Atlassian application is now aware of the other applications, plugins no longer need to be manually configured to provide the URL of the associated instance name, as long as the plugins have been updated to rely on AppLinks. There are two examples of plugins which already do this:
The JIRA FishEye plugin will check for AppLinks, and if AppLinks is configured for a FishEye instance, will not require further manual setup. The FishEye plugin gives you visibility into your source repository through JIRA – see source and changes in your code at the project and issue level.
The FishEye plugin in use on a JIRA issue
FE JIRA.png
The Activity Stream plugin gives the user visibility into activity across applications from the JIRA dashboard, and so is an obvious candidate for AppLinks usage. If you’re running JIRA/Confluence/FishEye/Crucible, installing the AppLinks and Activity Stream plugins will let your users track activity for a single project, all projects, or for a given user.
Activity Stream
stream.png
Going forward, we will continue to expand the uses of the AppLinks plugins, both from an ecosystem perspective (working with plugin developers to build AppLinks reliance into their plugins) and within the products themselves. There are a tremendous number of ways that AppLinks can be leveraged to make Atlassian applications work better together, and we’ve only just begun to scratch the surface.
Interested in learning more? Please follow the links below to the plugin home pages. And if you’d like to take advantage of all the features these plugins have to offer without having to set it up yourself, check out JIRA Studio.
AppLinks documentation
Confluence AppLinks Plugin
JIRA AppLinks Plugin

Fresh ideas, announcements, and inspiration for your team, delivered weekly.

Subscribe now

Fresh ideas, announcements, and inspiration for your team, delivered weekly.

Subscribe now