Issue Summary

Jira macros are not fixed with Jira macro repair tool.

Steps to Reproduce

1. Create an application link between a Jira and Confluence on-prem, name it, for example, "App link to JIRA".
2. Create some Jira macros on some Confluence pages. This will be created using the "App link to JIRA" app link.
3. Delete that application link and recreate it using a different name, for example, "App link to Jira".
4. Flush the Application Links cache or restart Confluence
5. Create some Jira macros on some Confluence pages. This will be created using the "App link to Jira" app link.
6. Migrate both Jira and Confluence to the cloud
7. Execute JMR, and have the following mapping, for example,
   • "App link to JIRA" -> "System JIRA"
   • "App link to Jira" -> "System JIRA"

Note that the application link ID is generated from the products' manifest files (it's dependent on their IDs). That's why, after recreating the app link, the ID will still be the same—the information on the manifest file won't change.

Expected Results

All occurrances from "App link to JIRA" and "App link to Jira" will be mapped to "System JIRA".

Actual Results

Jira macros are not fixed.

The below exception is thrown in the Splunk logs:

  level: WARN
   logger: com.atlassian.confluence.impl.jira.validator.ValidatorImpl
   m: { [+]
   }
   message: Empty serverId or serverName found

JMR logging stopped with the below message

Empty serverId or serverName found	21
Jira macro changed, pending save	129
Processing body content of page	1
Processing macro on page	129

Workaround

Currently, there is no known workaround for this behavior. A workaround will be added here when available.
Contact Migrations support via our support portal.