-
Suggestion
-
Resolution: Duplicate
-
None
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."
- duplicates
-
AUTO-34 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.
- Closed
- is related to
-
AUTO-34 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.
- Closed
- relates to
-
AUTO-113 Automation integrations with Marketplace apps - ability to trigger scriptrunner or any groovy script via Jira Automation
- Closed