Summary

In Team-Managed projects using Jira Work Management, when moving a story that is a child of an Epic, Jira lets you transform it to an Epic issue type but the parent link is not removed, causing to have a new Epic child under parent Epic and also a duplicate of the recently transformed Epic in the issue list.

Expected Results

Jira warns the customer about the parent link will get removed and then remove the parent link when the issue type changes to Epic.

Actual Results

Jira warns the customer about the parent link removal before it transforms the issue to an Epic but keeps the parent link after conversion, causing an inconsistency on the issues hierarchy and also creates a duplicate. 

Steps to Reproduce

1. Create a business team-managed project
2. Create an Epic issue in Project
3. Create a story an associate it with the created Epic
4. Change the Story issue type to Epic by using the Move option

Workaround

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