-
Bug
-
Resolution: Duplicate
-
Medium
-
11
-
Severity 2 - Major
-
Summary
After performing a JIRA Site Import and a Confluence Import from another instance the remote links from JIRA to Confluence display 'Page Failed to load' as both the appId and pageId have changed.
Steps to Reproduce
- Create instance-a containing JIRA Cloud and Conlfuence Cloud
- On instance A create an issue and then refer to that issue from a Confluence page
- Take a site backup and space backup of JIRA and Confluence
- Import the JIRA Site backup into instance B
- Import the Confluence space backup into Instance B.
- View the JIRA Issue on instance B
Expected Results
A remote link to the page on instance B exists.
Actual Results
The remote link on instance B says:
Page Failed to load
If you check the database the pageId and appId will not match the space export.
Workaround
As both the pageId and appId have changed it's nearly impossible to map the pages back in any automated fashion. Recreating the links will be your best option.
- duplicates
-
MIG-98 Confluence links in Jira issues should be updated automatically based on the new applink configurations
- Closed
- is related to
-
-
- Closed
-
![[Extranet] Page](/images/icons/generic_link_16.png "[Extranet] Page"){kind=icon}
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JRACLOUD-65278] Remote links fail to load after any confluence import due to changing appId and pageId
Hi All,
Is there any workaround for this issue (migration from cloud to server)?
Roman Vollenweider
added a comment - We have hundreds of Confluence pages with links to JIRA items, so recreating the links is not an option... I hope that a fix is provided soon!
Roman Vollenweider
added a comment - We have hundreds of Confluence pages with links to JIRA items, so recreating the links is not an option... I hope that a fix is provided soon! 
Sebastien Bonami
added a comment - I'm migrating from Cloud to Cloud by the way. Sebastien Bonami
added a comment - I'm looking for a solution ASAP. Anybody has solved this? Recreating the links is not a reasonable option.
Sebastien Bonami
added a comment - I'm looking for a solution ASAP. Anybody has solved this? Recreating the links is not a reasonable option. 
Paul Hooper
added a comment - Do you have a workaround ? This also happens when migrating from Server to Cloud, when you have a Confluence entities.xml uncompressed bigger than 200MB where the only option is to do a full JIRA import and then Confluence space by space import.
This is something that must be added to the documentation here https://confluence.atlassian.com/cloud/restricted-functions-in-atlassian-cloud-apps-744721664.html
This bug is being resolved as a duplicate of another bug. We will provide updates on the other bug. Please watch the other bug for future updates.
Thanks,
Vik
Atlassian Cloud Support.