Issue Summary

When using Bulk operations in Jira to move issues from a team-managed project to a company-managed project, the issues are being seemingly grouped by parent/epic link. For customers who use epics in a team-managed project, they will see a large number of grouping based on the number of epics. They then need to select the destination project for each group which is cumbersome and not intuitive.

Steps to Reproduce

1. Create a new team managed Kanban project
2. Create a couple of epics
3. Create a few test Task issues and assign them to either of the epics
4. Do a search for all issues in Jira from the above project
5. Select the option to Bulk change all issues from (...) menu on the top right of the search page
6. Select the option Move issues as the operation
7. In Step 3, note that issues are being grouped together by what seems to be the epic. Epic name itself is not displayed so user has no way of knowing which is which.

Expected Results

You will see all the issues that have been chosen to be moved grouped by their current project and issue type i.e 1 group per issue type per project.

Actual Results

There are multiple groups of issues displayed which have the same project and issue type.

Note that there are multiple grouping of the Task issue type. This is due to issues actually being grouped by parent/epic. If there are a lot of epics and related child issues then this screen will display a large list of items grouped by epic as a result. This would require a lot of button clicking to change the destination project and issue type across all groups.

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available.