Raised this improvement on behalf of customer

During a bulk move operation, I discovered that it is only possible to bulk move issues if I set the inactive accounts as active, otherwise either the assignee or reporter fields are prompted for.

I suspect this behavior is arising from the fact that a 'move' requires a 'create' to occur in the destination project, which in turn requires all users to be active, since it is not permitted to manually edit an issue's assignee or reporter to an inactive user.

However, in this particular use-case, it would be very desirable to be able to preserve the reporter and assignee even if the user account is inactive.

The ideal solution would be to permit a move operation to retain inactive users as either assignees or reporters.

Workaround

1. Temporarily activate the user
2. Perform the bulk operation
3. Deactivate the user

This would help retain the history of the issue correctly.