Regarding Jira Macro Repair

[Prajesh Krishna Karmacharya]

Hi, we are in a testing phase for migrating from Jira and Confluence Server to Cloud. We have tested the project migration in the testing phase...after migrating to the cloud as a test for some spaces, we found that Jira macro to be fixed...so can we use JIRA macro repair from confluence for specific spaces? What are the impacts of using JIRA macro Repair? Also, we followed your documentation, and the Existing JIRA instance link JIRA ID differs from the new JIRA instance link System JIRA.

Also, any process to back up our content or specific data if anything wrong happens after using JIRA macro repair.

[Alex Koxaras -Relational-]

Hi @Prajesh Krishna Karmacharya 

First and foremost. The place you asked your question is not Atlassian's support but its community. I hope that you understand the difference. Jira repair macro will repair any broken jira issue macro it will encounter and point to the right jira instance. From the selection on confluence settings you read:

The JIRA Macro Repair will find and fix any broken JIRA macros on your instance. If there are any broken links, we'll notify you, confirm your JIRA instance, and fix them up.
You can choose to Skip macro repair if you intentionally do not want your macros fixed. If you change your mind, you can come back to this screen and run the JIRA macro repair at any time.

Please note that when you run this, all the updates to those macros will be attributed to your name. This means that a new version will be created for each page containing a JIRA Issue macro that has been fixed. These changes will also appear in your All Updates feed, and anywhere else where your activity is being tracked.

Since you are on a testing phase I would go for it. This is why you test your migration prior of production migration.

[Alex Koxaras -Relational-]

And you can always ask for support from Atlassian, if you are eligible to do so.