All Versions
AppLinks 3.10 DocumentationAppLinks 3.5 Documentation
AppLinks 3.4 Documentation
More...
Once you have installed Application Links, you will need to configure the linked applications using the administration screens of each relevant application (JIRA, Confluence, etc).
Please install Application Links first
Before following the instructions below, please make sure that you have installed the Application Links plugin as described in the Installation Guide.
On this page:
There is no need to link AppLinks to a Subversion repository unless you have a specific requirement to do so.
The integration with Subversion provides a way for plugins to know what SVN repository a project is associated with. For example, Atlassian uses AppLinks primarily in JIRA Studio, where this feature allows JIRA Studio to create, update and delete repositories. However, there are currently no publicly-available plugins that make use of this functionality.
This means that, unless you are writing a new plugin to use the Subversion linking, you will not find it useful to add Subversion to your AppLinks suite. It will not provide any extra rendering of links in JIRA or Confluence. To render links of the form source:<Filename>
, you will need FishEye.
Below is a summary of the steps you need to take, to configure Application Links across your applications. These steps will get your Application Links up and running. For more detail and more complex setups, you will find links to further guides at the bottom of the page.
Make sure that the base URL is set correctly in each application which you intend to link. This is required for synchronisation to work correctly.
You will need to do this if you are intending to use Application Links with JIRA. If JIRA's Wiki Renderer is not enabled, JIRA link rendering will not work.
In JIRA, go to JIRA field configuration and enable the Wiki Renderer for the 'Description' field and other relevant fields, as described below.
If you run into problems, refer to the JIRA documentation for detailed instructions.
Now you will add each of your applications into the Application Links suite. The suite is the set of applications that you want to take part in the cross-application linking.
You can add applications via either Confluence or JIRA.
Field |
Description |
Examples |
---|---|---|
Application |
Select the application you are adding. |
|
Instance name |
Enter the name of the application instance. We recommend that you use a unique instance name, to ensure that synchronisation will work. |
|
URL |
Enter the address of the application instance. Please make sure that the URL agrees with the base URL configured in your application. For Subversion, the URL is {{ file:///}} plus the path to the SVN repository. (See the note about Subversion below.) |
For Confluence --- http://localhost:8080 Or --- http://myHost.com/confluence For FishEye --- http://localhost:8060 For Subversion --- file:///svn_repository Or --- file:///data/svnroot |
Login, Password |
Enter the username and password of a user with system administration rights on the application instance. They are not required for Subversion. |
|
FishEye Admin Password |
Enter the password of the FishEye administrator. This field is only required when you are adding the FishEye application. |
|
Application Links was originally developed for JIRA Studio, which uses the Subversion linking to associate the repository with the Atlassian applications. Outside JIRA Studio, there are currently no plugins that use SVN application links.
This means that, unless you are writing a new plugin to use the Subversion linking, you will not find it useful to add Subversion to your Application Links suite. It will not provide any extra rendering of links in JIRA or Confluence. To render links of the form source:<Filename>
, you will need FishEye.
Follow the steps above, to add any of the other supported applications into your Application Links suite.
If you have two or more instances of a particular application, you can add them individually. For example, if you have two Confluence sites, you can add them both.
If you need more information about adding multiple applications, refer to More about Adding Applications.
You can add an application to your Application Links suite via the JIRA or the Confluence administration screens. The added application will then appear in the list on the administration screen where you added it.
Now you need to synchronise with the other applications in the Application Links suite. This will let the other applications know that a new application has been added to the suite. For example, if you added a Confluence application via the JIRA administration screens, you should synchronise so that the Confluence application knows it is linked to JIRA.
If you need more information about synchronisation, refer to Synchronising Application Instances.
You can add your project links via either Confluence or JIRA.
Project links allow you to associate a particular Confluence space with a particular JIRA project, or a particular Crucible project with a JIRA project, etc.
If you have more than one instance of the same application (for example, you may have two Confluence sites), you can link a project to the primary application instance or any other instance. (If you are not sure what a primary instance is, please refer to Specifying a Primary Application Instance.)
-- Default Instance --
'.-- Default Instance --
'.You can synchronise your project links via either Confluence or JIRA. We have used JIRA in our example below. You can perform similar steps using the Confluence space administration screens. See Adding and Synchronising Project Links via Confluence.
You can add a project link to your Application Links suite via the JIRA or the Confluence administration screens. The project link will then appear in the list on the administration screen where you added it.
Now you need to synchronise with the other applications in the Application Links suite. This will let the other applications know that the project link has been added. For example, if you added a project link from a JIRA project to a Confluence space via the JIRA administration screens, you should synchronise so that the Confluence space knows it is linked to the JIRA project.
Due to a current limitation, the instance that you are synchronising from must be called 'jira' if you are synchronising from JIRA, or 'confluence' if you are synchronising from confluence. See APL-2.
Application Links Installation Guide
Application Links Documentation Home
Atlassian Product Integration