Summary

When moving a story that has an Epic Link to another project JIRA lets you transform it to an Epic issue type and the Epic Link field is not cleaned.

It also impacts next-gen projects, when we move a Story from a Classic project to a Next-gen project, the Story keeps the Epic link, letting the user associate the Story with a new Epic via parent link, and as consequence, the Story can have two Epics.

Steps to Reproduce

1. Create two projects
2. Create an Epic in Project
3. Create a story associated with that same Epic
4. Move the story to the second project changing its type to Epic

Expected Results

JIRA shouldn't let you select the issue type Epic when moving a Story with an existing Epic Link as this leads to an Epic being the son of another Epic which is an inconsistency in the relationship system of JIRA issues.
Another option is removing the value from Epic Link when the issue type is updated.

Actual Results

JIRA transforms the issue to an Epic and keeps the Epic Link causing an inconsistency on the issues hierarchy.

Workaround

For issue type changed:

1. Change the issue type back to the original issue type.
2. Remove the Epic link.
3. Change the issue type back to the desired issue type.

For issues moved between projects:

1. Move the issue back to the classic project.
2. Remove the Epic link.
3. Move the issue back to the original project.

For issues where even the Epic link is blank but the hierarchy is still not correct:

1. Move the issue back to Story type
2. Change again to the Epic issue type.