This documentation relates to Application Links 2.1.x
If you are using an earlier version, please view the previous versions of the AppLinks documentation and select the relevant version.

Skip to end of metadata
Go to start of metadata

Application Links is not supported by Atlassian. Many customers have reported issues with it, and compatibility varies by point release of Atlassian products.

We recommend you do not install AppLinks. We are working on a 3.0 release of AppLinks which will completely revamp the product. This will be bundled with our products, so you won't need to install it separately. As a bonus, it'll actually work.

The Development Hub is for people who want to create plugins, use the remote APIs or find out more about developing for the Atlassian products.

Plugin developers can make use of Application Links (AppLinks) to find out about other instances of Atlassian applications.

On this page:

Supported Applications

AppLinks supports the following applications:

Using the AppLinks API

You can use the AppLinks API to look up associated application instances and keys.




getLinkedApplication(applicationType, instanceName, localKey)

Get the linked application for the given application type, instance, and local key. The applicationType argument must be one of 'JIRA', 'CONFLUENCE', 'FISHEYE', 'CRUCIBLE' or 'SVN'. This method returns a com.atlassian.applinks.api.ApplicationLink object, which contains the remote URL of the application instance and the remote key that matches the supplied local key.

If another plugin wishes to use AppLinks, that plugin may include the AppLinks API classes in its jar, and use its application's specific component manager to find out if the AppLinks plugin is installed.

For example, in JIRA, you may use this code to detect if AppLinks is available:

if (ComponentManager.getComponentInstanceOfType(ApplicationLinksClient.class) != null)
    // AppLinks is installed

Application Links Documentation Home
Atlassian Product Integration

  • No labels
Write a comment…