-
Suggestion
-
Resolution: Unresolved
-
None
-
None
-
44
-
User Problem
When migrating from DC to Cloud, it is expected that links will be broken. The following KB outlines the process for handling this situation: After a successful Server to Cloud Migration, URL links are broken in the new Cloud instance
It is possible that the source environment has changed its URL multiple times throughout the environment's history.
Suggested Solutions
Please provide a way to perform link fixing that captures all source URLs.
Source URL | Destination URL |
---|---|
http://source.jira.server | https://<cloudsite>.atlassian.net |
https://source.jira.server | https://<cloudsite>.atlassian.net |
https://newsource.jiraserver.com | https://<cloudsite>.atlassian.net |
Links should be fixed based on the source URLs and updated to the new destination URL.
Current Workaround
None at this time. Only the current source URL can be used to perform link fixing.
Post Migration Link Fixing should be able to address multiple source URLs
-
Suggestion
-
Resolution: Unresolved
-
None
-
None
-
44
-
User Problem
When migrating from DC to Cloud, it is expected that links will be broken. The following KB outlines the process for handling this situation: After a successful Server to Cloud Migration, URL links are broken in the new Cloud instance
It is possible that the source environment has changed its URL multiple times throughout the environment's history.
Suggested Solutions
Please provide a way to perform link fixing that captures all source URLs.
Source URL | Destination URL |
---|---|
http://source.jira.server | https://<cloudsite>.atlassian.net |
https://source.jira.server | https://<cloudsite>.atlassian.net |
https://newsource.jiraserver.com | https://<cloudsite>.atlassian.net |
Links should be fixed based on the source URLs and updated to the new destination URL.
Current Workaround
None at this time. Only the current source URL can be used to perform link fixing.