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.

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Corrected links that should have been relative instead of absolute.
Include Page
_Note about Support
nopaneltrue
_Note about Support

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:

Table of Contents
minLevel2
maxLevel4

Supported Applications

AppLinks supports the following applications:

Include Page
_Enabled Applications
nopaneltrue
_Enabled Applications

Using the AppLinks API

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

com.atlassian.applinks.api.ApplicationLinksClient

Method

Description

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:

Code Block
java
java
if (ComponentManager.getComponentInstanceOfType(ApplicationLinksClient.class) != null)
{
    // AppLinks is installed
}
RELATED TOPICS

Application Links Documentation Home
Atlassian Product Integration