All Versions
AppLinks 3.10 DocumentationAppLinks 3.5 Documentation
AppLinks 3.4 Documentation
More...
This page tells you how to add applications to your Confluence site, so that Application Links will work between Confluence and the added applications.
Before following the instructions below, please make sure that you have installed the Application Links plugin as described in the Installation Guide.
Field | Description | Examples | |||||||
---|---|---|---|---|---|---|---|---|---|
Application | Select the application you are adding. |
| |||||||
Instance name | This is the name of the application instance. We recommend that the instance name is kept unique across all instances to ensure that synchronisation will work. There is a current limitation for synchronisation that the instance be called 'confluence'. See APL-2. | | |||||||
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.) |
| |||||||
Login, Password | These are the login details for the application instance. They are not required for Subversion. |
|
Anchor | ||||
---|---|---|---|---|
|
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.
Application Links Administration Guide
Application Links Installation Guide