Improve experience when importing a JSON file exported from server - the import tool just spins but no error is shown on the UI, process rules and report on failures.

When importing A4J rules from server, the importer is failing to parse the provided JSON, and meaningful errors are in the response, but only a spinning progress is displayed, leaving the user thinking it is just taking long to process.

In Automation for Jira on the Server and Data Center version, there are some automation rule actions (Publish event, e.g.) that does not exist in Jira Cloud, which is why the error is shown.

Using browser dev tools we see: 

0: "Error parsing provided JSON. Please ensure it was created using 'Export rules' previously. If the problem persists please contact Atlassian support! Error: IllegalStateException: Component for type ComponentTypeKey\{component=ACTION, type='jira.xxxxxxxx'} no longer exits."

This must be improved to show the exact error on the UI instead of spinning in a white screen forever.

***

When importing A4J rules from Server and Data Center platforms, the importer may report failures to parse the JSON file when the overall JSON is valid with errors related to a single rule or subset of rules. In these cases where the JSON is valid, continue on error and report on rule failures once completed for later action.

During import, the import tool just spins but no error is shown on the UI, which is due to the component not being supported in the cloud but the JSON is valid.

"Error parsing provided JSON. Please ensure it was created using 'Export rules' previously. If the problem persists please contact Atlassian support! Error: IllegalStateException: Component for type ComponentTypeKey\{component=ACTION, type='jira.xxxxxxxx'} no longer exits."

"Error parsing provided JSON. Please ensure it was created using 'Export rules' previously. If the problem persists please contact Atlassian support! Error: IllegalStateException: Component for type ComponentTypeKey {component=ACTION, type='com.onresolve.jira.groovy.groovyrunner:execute-script-issue-action-v2'} no longer exits."