-
Type:
Suggestion
-
Resolution: Unresolved
-
Component/s: Fixing Broken Links
-
None
-
3
Issue Summary
1) Involved instances: A (migration source) / B (migration destination) / C (third intstance)
2) It should be possible to update links in instance C that point to A so that they point to B after migration.
This JAC ticket proposes enabling the link fixing feature in Admin Hub to allow administrators to update links within a third instance (C). Customers managing multiple instances may plan a migration from Data Center A (source) to Cloud B (destination). After the migration, links in instance B that point to A can be updated to point to B using the existing link fixing feature. However, it should also be possible to update links in a third instance (C) that point to A, so that they point to B after the migration.
For example,
- A instance's page (ID: 12345) is migrated to B instance (Mapped ID: 67890).
- C instance's page has a link that points to A instance's page described above, such as https://A.datacenter.com/pages/viewpage.action?pageId=12345.
- This request is to update https://A.datacenter.com/pages/viewpage.action?pageId=12345 to https://B.atlassian.net/pages/viewpage.action?pageId=67890 in C instance's page.
Steps to Reproduce
Not available - Not supported today.
Expected Results
Can update the links in the 3rd instance to reflect a specific migration.
Actual Results
Not available - Not supported today.
Workaround
No workaround found; Custom script or manual work is only available.