Ability to map issue types in a single step while moving issues from Team managed to Company managed projects

Current behaviour:

When issues are moved from Team managed to Company managed projects, while mapping the source issue types to the destination project issue types, we see that the same issue type (Example: Task or Story or Bug) is prompted multiple times to be mapped.

We notice that this is because the Task/Story/Bug issue types are being grouped by child issues in Epics during the mapping operation.

For example:
If there are 6 issues of type "Task" belonging to Epic 1 and 2 issues of type "Task" belonging to Epic 2, then while moving all issues from team managed to company managed project, the issues of the same issue type "Task" are being prompted twice for mapping

• 6 issues of issue type Task from Epic 1
• 1 Issue of issue type Task from Epic 2

Suggestion:

It would be convenient if the issue types can be mapped in a single step instead of mapping the same issue types multiple times.