Application Links User Guide

Added by Sarah Maddox, last edited by Sarah Maddox on Aug 13, 2008  (view change)
All Versions
Click for all versions
AppLinks 1.1 Documentation

Index

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. <Review Number> CR-TEST-34567

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
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.

Comments (3)

 

  1. Sep 09

    Bob Swift says:

    I am confused on linking to Crucible reviews. The CR-TEST-34567 link - does tha...

    I am confused on linking to Crucible reviews. The CR-TEST-34567 link - does that mean review 34567 for the CR-TEST project or the TEST project? In other words, does the automatic linking only work if the naming convention of the Crucible project key starts with CR-? Or is it the users responsibility to remember to put CR- in front of the key normally used in Crucible? Thanks.

    1. Sep 23

      James Roper says:

      Hi Bob, This is a current limitation in AppLinks, and comes about because Cruci...

      Hi Bob,

      This is a current limitation in AppLinks, and comes about because Crucible review keys have the same structure as JIRA keys, so there's no way to differentiate them. This was worked around in JIRA Studio (which is where AppLinks comes from) by enforcing that all Crucible projects start with "CR-". So currently, CR-TEST-34567 is review 34567 for the CR-TEST project.

      I have created an issue in JIRA https://studio.atlassian.com/browse/APL-21 to allow rendering links to projects that don't start with CR-, if this is a feature you'd like to see, please vote on the issue.

      1. Sep 26

        Bob Swift says:

        Actually, I am fine with having a crucible project naming convention that includ...

        Actually, I am fine with having a crucible project naming convention that includes CR-. I am just trying to determine what your convention is so I can implement it. You have clarified that the crucible project is CR-TEST and I will change our naming convention to match. The only one that doesn't satisfy this is the default project CR. I can't delete it (at least on 1.5.1), but I would like to rename it!

Add Comment