Move Child Issues Does Not Preserve Epic Link if Next-Gen Epic Issue Type Has Been Renamed

Issue Summary

When moving issues from a next-gen project to a classic project, you are prompted to include child issues if they were not already a part of the initial list of issues to be moved. Selecting this option moves the child issues and where Epic issues are moved sets the Epic Link of the child issues accordingly in the destination project. However, if the Epic issue type was at some point renamed in the source next-gen project, the Epic Link is not populated in the destination project for the moved child issues despite mapping the renamed issue type to the Epic issue type in the destination project.

Steps to Reproduce

1. Create a source next-gen software project and a destination classic software project
2. Rename the Epic issue type in the source next-gen project to something else, for example 'Project'
3. Create a 'Project' issue in the next-gen project and several child issues under it
4. Move the 'Project' issue to the destination classic project, selecting the option to move child issues
5. In the resulting move operation screens, map the issue types to the corresponding issue types in the classic project, mapping the renamed 'Project' issue type to the default Epic issue type in the classic project
6. Execute the move operation

Expected Results

The 'Project' issue is moved to the classic project along with its child issues. The child issues have their Epic Link set to the parent issue accordingly.

Actual Results

The issues are moved but the child issues do not have their Epic Link populated with the moved parent issue.

Workaround

Change the name of the renamed Epic issue type in the source next-gen project back to 'Epic'. This will allow the auto population of the Epic Link to occur for moved child issues.