Issue Summary

It seems there was a regression of the fix for JRACLOUD-39112 (closed as Fixed)

On moving Issue to another project, JIRA doesn't check the permission for Assignable User. JIRA should not fill that Assignee field during moving an issue, if the former assignee doesn't have Assignable User in project B.

Steps to Reproduce

1. Create an issue in projectA
2. Give UserA Assignable User permission for projectA
3. Assign the created issue in projectA to UserA
4. Create projectB
5. Move Issue from projectA to projectB

Expected Results

Assignee field should be left blank as they original assignee doesn't have permission in projectB.

Actual Results

The original assignee is still assigned the issue in projectB although he doesn't have Assignable User permission in projectB

Workaround

No workaround available.