We are in the process of migrating all our Atlassian server products to cloud.
We use Confluence quite a lot and also have a public space where we link to pages from multiple places.
One idea was using DNS. but after trying to migrate the space we can see the URLs now include a unique pageID for all pages.
This would make it nearly impossible to remap the URLs.
I'm presuming we aren't the only ones linking to specific pages, in tutorials, email, etc.
How have you solved this issue?
Any updates to this issue? We are planning on migrating Confluence to the Cloud and have hundreds of links throughout our Data Center Spaces that link back to other Confluence Data Center pages, which will break once we decommission Data Center.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi, @Jesper Amelie from the Appfire team here!
That's a tricky one! We recently had a customer struggling with a similar challenge, and they used our marketplace app, Power Scripts, to fix their broken Confluence links after migrating.
Here's a demo of how you can update those Confluence links at once using Power Scripts: https://youtu.be/F82-6z5hdRw?t=967
If you need help building the concrete automation, our amazing support team is happy to help you along the way!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
That demo addresses updating links to Confluence that are within Jira.
How does that help with updating links to Confluence when those links are embedded in other places rather than Jira?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi, @Trudy Claspill – I see, thanks for clarifying.
You're right, when the links are embedded in places other than Jira, it's a bit more complicated.
In that case, there's no straightforward solution. One thing you could do is create an auto-redirect of those old Confluence pages to their new equivalent (and let automation do the lookup for what the new link should be). However, this basically only buys you time to fix links manually (and it requires you to keep the old Confluence up for a while).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yeah, that has also been our conclusion.
Make a list of all our deep links and then manually fix them :(
But thanks for the input
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.