Issue Summary

JCMA is unable to migrate the screens assigned to transitions when using the default configuration of the classic default workflow.

While the classic default workflow exists on both Cloud and on-prem, migrating a workflow based on it with JCMA might break screen association.

Steps to Reproduce

1. Create a Jira Software Project on a Jira Server instance
2. Go to the project's settings area -> Workflows -> Add workflow -> Add existing
3. Choose the classic workflow to add to the project and associate it with an Issue Type
4. Publish the workflow (after doing the statuses association)
5. Confirm that you can see the project workflow's transition Reopened display an association with the screen Workflow Screen via the classic default workflow association
6. On Server, going to the transition in the workflow, you can confirm the association (in the UI) between the screen and the transition:
7. Test the transition by closing and reopening one Jira Issue and confirm the screen will pop up
8. Migrate this project with JCMA

Expected Results

• Data preparation should be successful and project should get migrated successfully

Actual Results

• JCMA data preparation gives false error for invalid screen association with transitions.

[mri:mig:jira/classic:workflow:classic default workflow] The workflow '<name>' with transitions: Close Issue, Reopen Issue, Resolve Issue, Stop Progress, Close Issue are linked to invalid screens. [JCMA 151] Use the troubleshooting page to fix this error. Open the troubleshooting page using the URL below and use the error code (starts with “JCMA”) from the error to locate the fix in the troubleshooting page.
https://support.atlassian.com/migration/docs/troubleshoot-migration-with-jira-cloud-migration-assistant/#Data-preparation-errors 

Workaround

• Downgrade JCMA version to 1.17.1