Bulk change linked issues from external to local

[Christopher Moriarty]

My team uses both Jira Service and Jira Software projects, although for some reason they were created on completely different sites.  I recently worked with Atlassian to use their cloud migration feature to combine the two sites to leverage better automation between our service and software projects. 

The problem is that after the migration, the service tickets maintained their links to the old software site.  So now I have a backlog of service tickets with links pointing to the now archived external site, with a license that will expire eventually.  

One fix is to manually make new links to the local version of the same ticket, although I'm hoping there is a way to solve this in bulk!   

[Trudy Claspill]

Hello @Christopher Moriarty 

The Bulk Change feature in Jira Cloud does not let you bulk change links.

You might be able to work something out with an Automation Rule, but I have not tried to work out the details.

I have not done a cloud-to-cloud migration, but when I have done dc-to-cloud migrations the Atlassian support team has assisted with the update of such links in the Cloud instance by doing direct updates against the database for us. You may want to reach out to Atlassian support again to see if they can assist you in the same way.

[Christopher Moriarty]

Thanks @Trudy Claspill, I am also working with Atlassian support, and I've passed your comments along to them.  

[Christopher Moriarty]

Atlassian opened a new ticket specifically for this, and assigned a cloud migration support engineer to fix the links.  Thanks again for your suggestion!

[Christopher Moriarty]

I spoke too soon... In a bizarre turn of events, the support engineer now says they are unable to fix the links still pointing at the old site.  

[Trudy Claspill]

Did they give a reason?

[Christopher Moriarty]

They said: "the links you referred to is a remote link and these link fixes are not supported for Cloud to Cloud migrations."

They referenced the following knowledge base article, saying this limitation was partly mentioned in it:
https://confluence.atlassian.com/confkb/legacy-link-fixing-after-a-successful-server-to-cloud-migration-url-links-are-broken-in-the-new-cloud-instance-1271267903.html 

Kinda humorous they'd link to a page marked "This page is obsolete for most cases".