FAQ
In this section, you will find a comprehensive overview of all the common errors that may occur during the import process, along with strategies for effectively addressing them.
Validation errors are most likely caused by invalid data or errors in your JSON file. Re-exporting the workflow(s) and importing the newly generated JSON file will usually resolve any issues where no quick fixes are offered.
If you encounter an issue with the Workflow WIzard that you are unable to resolve, our Support Team is available to assist you.
Quick Fixes
Workflow already exists
📖 Description: This error occurs if your Jira Instance already contains a workflow with the same name as the workflow you are trying to import.
💡 Solution: To resolve the conflict, we provide a 'Quick Fix' button. Upon clicking it, an input field will appear. Simply enter a new workflow name and press 'Apply.'
Manual Action Required
Workflow refers to a missing status reference / Transition references an
unknown status
📖 Description: This error is caused by an incorrect 'status reference' property in your JSON file. A workflow or a transition is referencing a status that is not listed in the 'status' property at the beginning of the JSON file. The status reference needs to be a valid UUID.
💡 Solution: To resolve this error, you should export the workflow again and ensure that the JSON file is not altered afterwards. Alternatively you can fix the status references in your JSON file manually.
Transition refers to a status that does not exist within this workflow
📖 Description: A transition is referencing a status that is not included in the workflow's 'status' property. The status reference must be a valid UUID.
💡 Solution: To resolve this issue, export the workflow again and ensure the JSON file is not modified afterwards. Alternatively, you can manually correct the status references directly in the JSON file.
❗ Additionally, this error might cause some related errors.
Status should have an inbound transition
📖 Description: Every status in the workflow must have at least one transition leading to it. Each status reference must be a valid UUID.
💡 Solution: You can fix this error by reviewing the workflow transitions in the Jira instance from which it has been exported. Re-export the workflow and ensure that the JSON file remains unaltered afterwards. Alternatively, you can manually correct the status references directly in the JSON file.
❗ Additionally, this error might cause some related errors.
Unexpected token / Expected <some syntax element> in JSON at position x (line y column z)
📖 Description: This error occurs if the structure of your JSON file is incorrect.
💡 Solution: Re-export the worklfow or examine the error at the given position in your JSON file to correct it manually.
Rule cannot be applied to this type or is unsupported / This rule can't be
added to this workflow
📖 Description: This error occurs if a 'ruleKey' property contains an invalid key.
💡 Solution: Re-export the worklfow to resolve this error and ensure that the JSON file remains unaltered afterwards.
ValidateAFieldValidator has an invalid rule type
📖 Description: This error occurs if a 'ruleType' property contains an invalid type.
💡 Solution: Re-export the worklfow to resolve this error and ensure that the JSON file remains unaltered afterwards.
Other errors / Manual action required
📖 Description: There might occur other errors which are not stated above. They can appear if the JSON file is suffering from other syntactic or semantic inconsistencies.
💡 Solution: In every case, the issue can be fixed by re-exporting the workflow and keeping the JSON file unaltered before starting the import process.