Page Comparison

Linking to an issue on another JIRA instance. When this is done through application links, JIRA automatically brings in additional information from the remote system like summary and status. When done without an application link, the link just becomes a web link.

There can only be one remote link to the same JIRA server issue. Attempting to add another one with the same application link and issue will replace the existing link.

Reverse links

• A reverse link will be established if there is an application link on the target server pointing back to the source server and the reverseLink parameter is specified. The reverseLink parameter specifies the link description of the reverse link. If blank, the link description is defaulted by JIRA.

• JIRA 7.1.0 is the name of an application link

--action addRemoteLink --issue XXX-1 --toIssue SUPPORT-123 --targetServer "JIRA 7.1.0" 
    --link "Support issue"

--action addRemoteLink --issue XXX-1 --toIssue SUPPORT-123 --targetServer "JIRA 7.1.0" 
    --link "Support issue" --reverseLink "Development issue"

Confluence page linking can be done by providing a url to a Confluence page that contains a pageId request parameter. It also requires a Confluence application link with a url that partially matches the url of the page being linked. Without an application link, it will just be a web link. If a pageId is not available, the UI will show a page loading error! A url with a pageId can be obtained in a number of ways:

• The url when editing the page or copied from the Edit link
• The url for Attachments
• The url for Page Information

Reverse links

• We are not able to support at this time. Watch

  Jira Legacy
  JCLI-867 JCLI-867

  .