-
Bug
-
Resolution: Duplicate
-
Low
-
None
Assuming we have 2 OnDemand JIRA+Confluence instances, lets call them A and B. If we first import JIRA (all content) from A to B then we import one space from Confluence, again from A to B, we have broken JIRA Issues macro in the space in B.
The following error is shown instead of the issues:
It reads:
JIRA Issues Macro: Unable to locate JIRA server for this macro. It may be due to Application Link configuration.
Since JIRA in instance B has the same content in A, we would expect JIRA Issue Macro to be able to find the issues, since the JQL remains the same.
Steps to Reproduce
- Have a JIRA + Confluence OnDemand (A) with projects and issues in JIRA
- Create a space in Confluence and create pages with JIRA Issue macro linking to issues in JIRA
- Have another JIRA + Confluence OnDemand (B) instance
- Full export JIRA in A and import in B
- Export the space created in A and import it in B
- JIRA Issue macros will be broken
Workarounds
- Edit each JIRA Issue macro individually
- Click the 'magnifying glass' to 're-search' for the issues
- Confluence will find them
- Insert again the macro and save the page
- duplicates
-
CONFSERVER-31026 Confluence Space Export/Import Affects JIRA Issue Macro Links
- Closed