Applinks fail when copying Jira and Confluence to other environments
Platform Notice: Server and Data Center Only. This article only applies to Atlassian products on the server and data center platforms.
When moving JIRA and Confluence to a different environment, most of the time in order to test, links between the two instances break. The new environments have different URLs, which affects the issue link in JIRA and page links in Confluence as they rely on application link which has been defined earlier on the older environment.
A resolution to this issue for Confluence can be found at How to bulk update JIRA Issue Macro to point to a different JIRA instance. For correcting the issue in Jira, see below.
this page does not apply for project import.
The new environment is using a different address. Links in JIRA and Confluence are dependent on the original application link.
Jira has a great XML Backup utility and XML backup contains the data (include links). Hence, you can use the following steps to update the links in Jira.
The approach to achieve this issue is:
- Take a backup of Jira: Backing up Jira.
- Extract the backup file.
- Open the entities.xml file in Notepad or another text editor.
- Search/replace the old Confluence link with the new one (according to your new environment). The replacement options can be found at How to replace all hard coded links after a base URL change.
- Restore the data to JIRA following our documentation: Restoring data.
We highly recommend customers to avoid direct database modification.
XML backup may not be a suitable solution for medium or large size instances of Confluence, so we don't recommend users to replace the links by editing the Confluence XML backup. Instead, we suggest customers to bulk edit the links from the database to replace the old Jira link with the new one (according to your new environment).