Summary

In a workflow transition screen, when a field is set as required and not filled in, the "Assignee" field will display the username rather than the display name of the user. If that value was changed in that screen, it won't save the change to the issue.

Environment

• Jira 7.3.6, 7.6.6 + Jira Suite Utilities
• Jira 7.7.2, 7.9.0, 7.9.1, 7.13.0 - able to reproduce just by marking field required in field configuration;

Steps to Reproduce

1. Create a project with:
   • One or more fields as required in a field configuration;
   • One or more transitions in the workflow containing a screen with the "Assignee" field mapped;
2. Create an issue in that project;
3. Set the assignee to "User A" (username 'usera');
4. Trigger a workflow transition;
5. Change the assignee to "User B" (username 'userb');
6. Make sure one or more of the required fields are blank;
7. Submit the transition. You will get warning for other mandatory fields;
8. Now, you may notice that Assignee is changed from the display name of the chosen user to their username;
9. Fill the other required field/s without touching the "Assignee" field;
10. Submit the transition again;
11. You can see Assignee field still retains the previous value, from before executing the transition;

Workaround

Ensure the assignee field is filled out with the intended value - the chosen user's display name with their profile picture.

Expected Results

The "Assignee" field should show the user's display name at all times, and changes to the field should be saved without requiring additional input.

Actual Results

Assignee field shows the username instead of the user name and ignores changes during a workflow transition.