Issue Summary

The issue arises when a transition screen with validators fails. At this point, the relationship between the user listed in the dropdown (Assignee) and the corresponding Atlassian Account appears to be broken, leading to the disappearance of the user's logo. Consequently, the user field remains unchanged, even though a different user name is selected from the dropdown.

Steps to Reproduce

1. Create a new screen with two fields: Assignee and any desired custom field.
2. Add a validator to the custom field, making it a required field.
3. Associate this screen with a transition.
4. Assign a Jira Issue to a specific user.
5. Transition the issue using the transition mentioned in step 3.
6. Change the Assignee to a different user while leaving the custom field empty to trigger the validator failure, and submit the transition.
7. The validation should fail, and the custom field missing error should be displayed.
8. Complete the previously missing custom field and submit the transition again.
9. Observe that the Assignee is not updated as expected.

Expected Results

The selected user should remain selected even after a validator fails.

Actual Results

The relationship between the user listed in the dropdown and the corresponding Atlassian Account appears to be broken, leading to the disappearance of the user's logo. Consequently, the user field remains unchanged, even though a different user name is selected from the dropdown.

Workaround

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