Jira won't group issues from the same issue type on a bulk move, if they belong to a different Epic, on a Next-gen project

Issue Summary

When bulk moving issues from a Next-gen project to a classic one, if there are issues from the same issue type belonging to different Epics, Jira won't group those issues within the same issue type during the process. It also won't warn admin from which Epic they belong to, making the process confusing. The video below better demonstrates the problem:

JRACLOUD-73590.mp4

Steps to Reproduce

1. Have a Next-gen project with 2 Epics (Epic 1 and Epic 2) and 2 child issues from the same issue type, one belonging to each Epic (Task 1 belongs to Epic 1 and Task 2 belongs to Epic 2, for example);
2. start the process of bulk moving all issues from the Next-gen project to another one;
3. Reach the screen to select which issue goes to which project.

Expected Results

Jira will either group the issue type in just a single line or will inform admins to which Epic that issue belongs to.
Given that, at this moment, the loss of Epic <> child relationship will happen in this process (of moving issues from the Next-gen project to the classic one), it would be better if Jira simply groups all issue types in a single line. According to our Migrate between next-gen and classic projects:

Jira moves your epics across if you map them to an epic issue type in your new project. But, you'll lose the relationship between your epics and their child issues. The child issues themselves will sill exist, but the links between them won't.

Actual Results

Jira shows multiple lines for the same issue type, making the process confuse.

Workaround

There is no workaround for this scenario. Despite no data will be loss, this just confuses admins.