All Versions

AppLinks 3.10 Documentation
AppLinks 3.5 Documentation

AppLinks 3.4 Documentation
More...

Application Links 1.x Documentation

Index
[Downloads (PDF, HTML & XML formats)]

This documentation relates to an earlier version of Application Links.
View this page in the current documentation or visit the current documentation home.

Skip to end of metadata
Go to start of metadata

Your system administrator can link your Atlassian applications together via Application Links. Once your applications are linked in this way, automatic cross-linking is supported between the relevant applications. This means that you can quickly and easily add text which will be automatically hyperlinked when you save the Confluence page or JIRA issue, etc. The link will 'know' which application it should point to. You do not need to enter the application's full address.

Automatic cross-linking is supported between the following applications:

On this page:

Creating Links from one Application to Another

To create a link, enter the text shown in the 'Type this' column below. The text is the same, no matter which application you are in.

To link to ...

Type this
(excluding the angle brackets)

Examples

a JIRA issue

<Issue Key>

TEST-123
ACME-456

a Confluence wiki page, in the default space. (Your system administrator can determine the default space by specifying project links and/or the primary Confluence instance.)

[<Page Name>]

[My Draft Page]

a Confluence wiki page, specifying a space.

[<Space Key>:<Page Name>]

[TEST:My Draft Page]

a changeset.

revision:<Changeset Number>
rev:<Changeset Number>
r<Changeset Number>  

revision:98765
rev:98765
r98765

a source file.

source:<Filename>

source:trunk/pom.xml

a Crucible review. (info) See the note on naming conventions below

<Review Number>

CR-TEST-34567

Naming Convention for Crucible Projects

For AppLinks to work, your Crucible project keys must start with CR-. For example, you might name your Crucible project CR or CR-MYPROJECT or CR-TEST (as in the example above).

Icon

This is a limitation in AppLinks. It comes about because Crucible review keys have the same structure as JIRA keys, so there is no way for AppLinks to differentiate them. In JIRA Studio (which is where AppLinks comes from), we worked around this by enforcing that all Crucible projects start with 'CR-'. Please watch and/or vote for APL-21 if you are interested in allowing links to projects that don't start with 'CR-'.

Example: Linking from a Confluence Page to a JIRA Issue

Let's say you have written a functional specification or a use case in Confluence, and you want to link to the JIRA issue which contains the original feature request.

  • Edit the Confluence page.
  • Enter the JIRA issue key, such as 'MYPROJECT-1'.
  • Save the Confluence page.
  • The JIRA issue on your page will automatically be linked to the issue on your JIRA site. See the screenshot below.

Screenshot: Creating links from a Confluence page to a JIRA issue



Example: Linking from a JIRA Issue to a Source Code File

Let's say you have a JIRA issue which requests the development of a new feature. You may want to add links in the JIRA issue, pointing to the source file(s) which implement the feature.

  • Edit the JIRA issue.
  • Enter 'source:' followed by the source file name in a text field, such as the 'Description' or 'Comment' field.
  • Save the JIRA issue.
  • The text on your issue will automatically be linked to the source file via your FishEye site. See the screenshot below, which shows a link from a JIRA comment.

Screenshot: Creating links from a JIRA issue to a source file



RELATED TOPICS

Application Links Installation Guide
Application Links Administration Guide
Application Links Documentation Home

  • No labels