-
Bug
-
Resolution: Fixed
-
High
-
5.3-OD-7, 5.3, 5.3.4, 6.0.0-OD-2016.12.1
-
OnDemand
-
92
-
Severity 3 - Minor
-
NOTE: This bug report is for Confluence Server. Using Confluence Cloud? See the corresponding bug report.
What had caused this issue?
The JIRA Issues Macro is used to create links to JIRA issues in Confluence pages. These links contain the identification of which JIRA instance the JIRA Issue Macro then will be referring to.
This issue occurred as Confluence A and Confluence B do not have the same Application Links configured.
JIRA Issue Macros' in Confluence B (imported from Confluence A via Space backup) aren't able to render the issues correctly as it is still referring to JIRA instance configured in Confluence A, in which is not configured in Confluence B.
Resolution for Cloud instances
The Confluence Cloud importer has been updated to provide a JIRA macro repair feature, in which any broken JIRA macros will be fixed as part of the import.
For more details on this, please refer to our Import the space content into Confluence Cloud document.
Workaround for Server instances
If you're using Confluence Server and you've recently changed domain name, migrated from Confluence Cloud, or merged multiple instances, you may need to relink JIRA issues macros.
For a workaround of this issue, please refer to the steps outlined in our How to bulk update JIRA Issue Macro to point to a different JIRA instance
Summary
Creating a backup of your Confluence Cloud Space to import into another Confluence Cloud instance affects JIRA issue macro with the warning:
"Unable to locate JIRA server for this macro. It may be due to Application Link configuration."
Steps to Reproduce
Export Space XML backup from Confluence A.
Import the generated XML backup to Confluence B.
Expected Results
Contents of the imported Space (JIRA Issue Macro in particular) are rendered successfully.
Actual Results
JIRA Issue Macros that exist in the imported space's pages are not rendered. Instead, the following warnings are shown:
"Unable to locate JIRA server for this macro. It may be due to Application Link configuration."
- is duplicated by
-
CONFCLOUD-54551 Importing Space After JIRA Import breaks JIRA Issues Macro
- Closed
- is related to
-
CONFSERVER-34994 Mentions broken after space xml Import
- Closed
-
CONFSERVER-32033 Application link Alias
- Closed
- relates to
-
CONFCLOUD-31026 Confluence Space Export/Import Affects JIRA Issue Macro Links
- Closed
-
JRACLOUD-65278 Remote links fail to load after any confluence import due to changing appId and pageId
- Closed
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...