Details
-
Type:
Suggestion
-
Status: In Progress (View Workflow)
-
Resolution: Unresolved
-
Component/s: Confluence - Migration assistant, Jira - Migration Assistant
-
UIS:16
-
Support reference count:138
-
Feedback Policy:
Description
NOTE: This suggestion is for Jira Cloud. Using Jira Server? See the corresponding suggestion.
Problem Definition
Currently When moving Jira and Confluence to a different environment, most of the time in order to test. The new environment has 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.
Suggested Resolution
Confluence links in Jira need to be updated as the new applink is created.
Temporary Resolution
This issue could be solved by taking the steps at Application Link Issue When Moving Jira and Confluence. However, this may not be applicable to Cloud since a full restore of Confluence is not possible when also Jira is present on the same instance. Therefore the page-ids may be different as well, not only the hostname, and changing only Confluence url in the backup file won't solve the issue.
In this case you contact Atlassian support by logging a request in support.atlassian.com and ask them to apply the workaround for this issue.
Attachments
Issue Links
- depends on
-
- In Progress
- is blocked by
-
- In Progress
-
- Closed
-
MTOOLS-13 Loading...
- is duplicated by
-
JRACLOUD-65278 Remote links fail to load after any confluence import due to changing appId and pageId
-
- Closed
-
-
-
- Gathering Impact
-
- is related to
-
-
- Closed
-
-
- In Progress
-
- Gathering Interest
-
- Gathering Interest
- resolves
-
-
- Closed
-
- mentioned in
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- was cloned as
-