Moving a project recreates Epics in the target namespace

Summary

When moving a project to another namespace, parent epics of the project's issues are recreated in the target namespace. This causes duplicate epics without relation to the original epics.

Steps to reproduce

I have not yet reproduced the issue, as it was reported by a customer. According to their report:

• Have a project that has issues with parent epics
• Move that project to another namespace
• Epics are created in the target namespace and assigned as parents to the project's issues

What is the current bug behavior?

Epics are created in the target namespace

What is the expected correct behavior?

The project's issues are still linked to the original epics. This would require epics to be accessible for linking across groups.

Alternatively, a note should inform the user that the issues relation to the epic was removed because it was transferred out of the epic's namespace.

Possible fixes