How to check which application link the Jira Macro repair should be mapped after an import
Platform Notice: Cloud Only - This article only applies to Atlassian products on the cloud platform.
Summary
After importing Confluence Cloud spaces from a different instance, the application links will either have a System Jira (if it is from an application link of the same tenant/URL) or the name of the application link if it is connected to a different URL/tenant.
ℹ️ As part of the import process, the Jira issues macro should be remapped by the administrator by using the Jira macro repair.
Although having the name of the application link helps, since the default and unchangeable name of the bundled application link is System Jira, it can cause confusion to confirm the mapping when the application link of the instance where the import came from is not linked as it would have the same name of the target Confluence. For example:
Solution
Identifying the links
To identify the links, there is already a suggestion in place:
As a workaround, the browser console can be used in order to find the application link IDs through the Elements part. This way, the user will be able to find the source of the System Jira application link where it is coming from.
When using the Jira macro repair having more than one instance imported, to ensure which System Jira is which, use the browser's console (right-click > Inspect) and then, check for the following options to find the application link id (under select name and id):
There, look for the ID used in the System Jira and then, compare it with the list of IDs also displayed in the console, right below the one so we can select the one that matches, under the Select an Application Link.
If we are not sure about it, to check from which Jira the ID is from, we can also access the Application Links part of the Confluence (through its administration) instances where the content has been imported from and then, use the console:
After ensuring about the ID to be used, feel free to select the corresponding option on the New Jira instance link part of the macro repair.
Notes
If the Jira content has not been imported, the Jira issues will not be located at the target's Jira instance linked to Confluence, meaning that they can be only "repaired" if an application link is created to the source where the Confluence import came from and then, the remap would be performed.
If the Jira issues are being imported via CSV to an existing project, creating a new app link would be the best method to directly link it with the ID found in the instance where it is coming from, via the method above with the Jira macro repair. Otherwise, it would be needed to manually change the issue key used to the new one that is retrieved in the CSV.
Was this helpful?