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.
In Confluence, links are located in the database and since XML backup may not be a suitable solution for large or medium size instances, we don't recommend users to replace the links by editing the XML backup. Thus, we suggest customers to bulk edit the JIRA link from the database.
Since JIRA has a great XML Backup utility and XML backup contains the data (include links), we can do thing easier in JIRA as explained.
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)
- Restore the data to JIRA following our documentation: Restoring data.
We highly recommend customers to avoid direct database modification.