Issue Summary

Jira gadgets aren't supported between Jira Server and Confluence Cloud.

Migrating customers need the ability to use these gadgets. Some gadgets can be used with the Jira Legacy chart macro.

• Pie Chart
• Created vs. Resolved
• Two Dimensional

Customers need a method to bulk-convert 

Confluence Cloud doesn’t include the option to register external gadgets, so you won’t be able to use any gadgets that you might know from server. Some cloud sites might still include the Activity Stream gadget (it was available without registering), but this gadget has been deprecated and is not available in new cloud sites.

Source: https://confluence.atlassian.com/enterprise/integrate-confluence-cloud-with-jira-server-1101925671.html#IntegrateConfluenceCloudwithJiraServer-jiragadgets

Steps to Reproduce

1. Install a Jira Data Center instance (you can use http://go/instenv-ui to do this) and create some test issues and a filter.
2. Install a Confluence Data Center instance and integrate it with the Jira Data Center instance created in the previous step.
3. Add external gadgets from the Jira Data Center instance on Confluence Data Center instance.
4. Add a Jira Gadget to a page within the Confluence Data Center instance.
5. Create a test Confluence Cloud Site and integrate this Site with the Jira Data Center created in Step #1 via Application Link.
6. Migrate to Confluence Cloud using CCMA.
7. Notice how the Jira Gadgets are broken post-migration.

Expected Results

The gadget is converted to supported options

Actual Results

The gadget appears with one of these errors

Error rendering macro 'gadget' : The gadget at https://JIRA_SITE.com/rest/gadgets/1.0/g/com.thed.zephyr.je:zephyr-je-gadget-testcase-execution/gadgets/testcase-execution.xml was not added to this Confluence instance yet.

OR

This gadget cannot be displayed on your dashboard. This could be due to a licensing problem or an application error. If you need this gadget, contact your administrator for assistance. Otherwise, you can remove it from your dashboard.

Workaround

Currently, there is no known workaround for this behavior. A workaround will be added here when available.