nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Issue links broken after Jira Software migration to cloud

Bo Bøgvald

Anyone knows how to fix broken issue links after migration of Jira Software to cloud?

I am testing migration one of our Jira Software instances to cloud. After migration and after recreating application links to Jira ServiceManagement and another Jira Software instance, I experience that links only works one-way. From the migrated Jira Software they work fine, but from ServiceManagement and the other Jira Software they are broken.

I guess it is because the Jira Software that has been migrated to cloud has got some sort of new ID, and therefore ServiceManagement and the other Jira Software does not "know" that the cloud instance has replaced the server instance.

Atlassian support is referring to some generic processes that is not specific enough for me to fix the issue:

You can recreate them using REST APIs as mentioned here group issue links
Or you can use the CSV import method to just import the links after the issues were migrated.

Any help is highly appreciated.

Best Regards

Comments

Janco Hoekstra_i6xvdi

Hi Bo

I had a problem like that and corrected the links over the rest API.
For this to work, you'll need to find a way to map the old linked issues to the cloud once.

In my case, I wrote a script in python, that looked up the issue link in the old on-prem and used a unique identifier (in my case a cf in the target issue). Then on cloud I let the script search for this identifier and changed the false link (cloud source issue) to be corrected to point to the found target issue in cloud.

I hope this will help.

Salim Richa

Did you try to migrate all the issues from the on-prem to the cloud?

Bo Bøgvald

We cannot migrate ServiceManagement due to contractual and GDPR considerations. The other Jira Software is in the cloud already. Still links break.

Ralf Becker_c5h6c3

We had the same issue, but there is a conveniant solution to this: the Atlassian-Support will do this for you. Keep Googling: there is an help article with SQL-queries you have to run on your Server-instance and send these results to the support. They will do the rest. Migrated 18k tickets and 36k pages half a year before, just found 1 or 2 cases where it did not work out.

Bo Bøgvald

Thank you very much, Ralf. Exactly what I need. I will Google, and discuss with Atlassian.

Bo Bøgvald

Thanks Janco. I will keep you advice in mind in case I cannot find any other solution. But I would prefer to avoid doing my own scripts if possible.

Paul Hecker_60magh

Hi Bo,
You have probably already found the relevant information, but for the benefit of others migrating Confluence to cloud, please refer to the information below.

Once the migration of Confluence to cloud completes, the first step is to run the Macro Repair Tool. It may require running the tool several times until the tool does not prompt for any more repairs. Running until you get an error free result is needed to identify and correct the links within the tool's repair scope.

Using the Jira Macro Repair
https://confluence.atlassian.com/confkb/using-the-jira-macro-repair-1084362152.html

As of January 2023, there is a know bug you should be aware of concerning the Macro Repair Tool. If you find that the Macro Repair Tool keeps prompting for the same repairs, wait 60 minutes to allow for any backend processing that might be running to complete, and try running the Macro Repair Tool again. If it is still prompting to make the same repair, please open a Support ticket with Atlassian. If you have been working with an Atlassian Cloud Migration Manager (CMM), you would need to follow their instructions on opening a Problem Ticket associated with the migration to get the proper assistance.

CONFCLOUD-73050 - Jira Macro Repair needs to be run multiple times after migration
https://jira.atlassian.com/browse/CONFCLOUD-73050

Once the Macro Repair has completed, or while Atlassian Support reviews the macro repair results as noted above, gather the information in the support document referenced below and open a support ticket \ problem ticket with Atlassian Support to run the Confluence Link Repair. Atlassian will need that information to run their link repairs.

After a successful Server to Cloud Migration, URL links are broken in the new Cloud instance
https://confluence.atlassian.com/confkb/after-a-successful-server-to-cloud-migration-url-links-are-broken-in-the-new-cloud-instance-1077781093.html

Please keep in mind that the link repair scripts take a significant amount of time to run, but Atlassian Support will update you when they start the link repairs and usually provide an estimate on when the repairs should complete.

I hope this information is helpful.

Regards,
Paul

Bo Bøgvald

Thanks much, Paul. Now, we are not migrating Confluence, only Jira Software, leaving Confluence and Jira ServiceManagement on-premise. Do you have similar information about how to repair broken issue links between:

Jira Software cloud and Jira Service Management on-premise
Jira Software cloud and Confluence on-premise
Jira Software cloud and other existing Jira Software cloud.

All help is highly appreciated.

Michele De Pascalis

Hi Bo, sorry to reopen this topic after so long: did you find a solution for this, eventually?

C_Faysal _CFcon_

After Server or Data Center to Cloud migrations, broken links are often caused by legacy base URLs still embedded in issue descriptions, comments, custom fields, or Confluence page bodies. These are not always fixed automatically, especially when issue keys changed or tiny URLs were used.

We built Legacy URL Scanner for Jira and Confluence to address this systematically. The app scans content for legacy instance URLs, classifies findings, and applies a rule based replacement pipeline with governance rules, RegExp patterns, and URL mappings.

It also supports automatic issue key resolution via JQL and detects Confluence tiny URLs, which are often missed by standard migration tooling.

This is particularly useful for post migration validation and controlled remediation at scale.

Happy to provide more details if helpful.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira-software

issue-link