Issue Summary

When migrating from the server to the cloud using JCMA, the fixVersion ID gets changed.After the migration of confluence pages,  the JQL which are all using fixversion ID in the Jira macro, will become invalid.

This is reproducible on Data Center: (yes) 

Steps to Reproduce

1. In Jira DC/Server, Create a sprint.
2. In Confluence DC/Server, Insert the JQL on confluence pages as mentioned in the article Insert the Jira issues macro. Ex: project = <PKEY> AND fixVersion = <ID>
3. Migrate the Jira project using JCMA and then migrate the confluence space using CCMA.

Expected Results

The fixVersion id should be updated in the JQL of the Jira Macro or the ID should remain the same after migration

Actual Results

The Macro results nothing as the JQL becomes invalid with wrong fixVersionID. Refer attached screenshots.

Workaround

Manually update the sprint ids in the confluence pages.