Moving a Jira task with sub-tasks to another project throws an error

Summary

Attempting to move an issue (task, story etc) that has sub-tasks from one project to another cannot be done as at the final step the user is given an error:

At least one of the issues you are trying to move has been recently updated by another user (<issue key>). Please cancel and start again.

Environment

Jira Cloud

Steps to Reproduce

1. Create one issue with one or more sub-tasks
2. Attempt to move that issue to another project
3. Map the destination status to reach the final step
4. Once the user clicks confirm at the final step, the error is thrown: At least one of the issues you are trying to move has been recently updated by another user (TS3-2). Please cancel and start again.
5. Of course, trying again yelds the same result.

Expected Results

The issue is moved together with its sub-tasks

Actual Results

An error message is thrown:

At least one of the issues you are trying to move has been recently updated by another user (TS3-2). Please cancel and start again.

Workaround

One workaround would be to create a task in the destination project and move only the sub-tasks. However, this is not practical for situations when the user needs to move multiple tasks together with their sub-tasks