Issue Summary

Jira issue edit action wasn't allowed with any of the user picker fields (System and Custom) containing a user value that has been deactivated. With the fix introduced in JRASERVER-38412, we now have the ability to edit the issue with a deactivated user in the Assignee and/or Reporter fields.

However, the issue edit action still doesn't allow if there's a User Picker Custom field (single/multiple) which has a deactivated user.

Steps to Reproduce

1. Create a user.
2. Create a single/multiple User Picker custom field and add it to relevant screens
3. On an existing or new issue, add the user in the User Picker custom field
4. Deactivate that user.
5. Attempt to edit the issue.

Expected Results

Jira allows you to edit the issue without having to remove the deactivated user from the User Picker custom field

Actual Results

Both Edit issue screen and inline edit stops users from editing the issue with the message:

User '<USERNAME>' is not valid for this user picker.

!2025-04-25_13-00-59.png|thumbnail

Workaround

• Remove the deactivated user from the User Picker Custom fields, where possible
• Re-activate the user for the time being - edit the issue - deactivate again