Generate a report of Epic links found on issues at and above the epic hierarchy level that are no longer migrated as of JCMA version 1.9.17

Issue Summary

In JCMA. 1.9.17, if the migration plan contained Epic links for issues at or above the Epic hierarchy level, a CSV report would be generated showing the parent-child relationships that would not be migrated. This functionality no longer exists in releases of JCMA after that version.  The affected parent-child relationships are not migrated, and no details of that non-migrated data appear in any post-migration reports.

This suggestion is to provide a way to identify the Epic-child relationships that were not migrated by JCMA.

Steps to Reproduce

1. Create a new issue type called Production Issue.
2. Add it to the same issue hierarchy level as Epic.
3. Create a new Jira project and include the Production Issue issue type.
4. Create an Epic.
5. Create a Story and add it as a child of the Epic.
6. Create a Production Issue and add it as a child of the Epic.
7. Migrate the project from server to cloud.

Suggested Results

On the pre-checks screen, JCMA will generate a CSV report indicating that this Epic-Production Issue relationship will not migrate to the cloud.

Actual Results

• No CSV report is created indicating that this Epic-Production Issue relationship will not migrate to the cloud.
• The project migrates to the cloud.
• The Production Issue issue type is created and added to the same hierarchy level as Epic as expected.
• All of the issues are created, but only the Story becomes a child. No log is created to indicate that the Production Issue ticket is not a child of the Epic.