Our team would like this feature as well especially for high profile users that we deactivate immediately before the request ticket is submitted. 

7a5455a58cb6 Thank you for the suggestion. We indeed have JSM; we don't have any good automation/workflows for the lifecycle management of Users as Assets yet, though it has been on our wishlist. This may be an excellent motivation to prioritize it.

4ecb2dbacb44  we were in the same situation as your team, but recently we have moved the process to rely on Asset object that represent an Employee. By doing that we have eliminated this annoying issue with inactive users. It also lets us better manage LOA processes, where user gets temporary disabled.

If you have JSM, I would recommend looking into it.

Same thing as 51b5940ab309 said. Our HR team sometimes sends out an email to terminate an employee before creating the ticket, and our IT guys are quick to term access in AD, and then when HR goes to fill out the ticket the user isn't available anymore. I know we can work on our process of doing the ticket first, but we have various automations/subtasks that happen during the offboard process that we still need to do, and we can't create the ticket for those other needs if the user name isn't selectable. This is a HUGE risk for us (security and compliance).

Would like to see the additional option of "Is Not Empty", to help bridge the gap.

Ditto to what Jeremy Carlson said.

I was looking at the Sprint field recently, and it has a switch to "show only sprints that belong to this project", a toggle like this to turn on inactive users would be great.

Same situation as below. If the user is disabled in AD before the ticket is created by HR, the user is no longer able to be selected. Not only that, when the user is disabled in AD therefor deactivated in Jira, it is causing user fields that had them selected to show "None" on the issue view. The user is still populated on the form itself.

Exact same comment as e3cc50a490c2.

Also: I link tickets based on a user field, but the automation fails when the user is inactive because the smart value doesn't return anything.

It would be nice to have this option added to the field context. We track employee departures in JSM and if the ticket isn't created in a timely manner, we're unable to associate the correct user with the ticket as their user account has already been deactivated.