Hi everyone , 

Filtering for User Picker (multiple fields) custom fields is now available in Jira.

Thank you so much for your input,

Saskia

Hi everyone , 

It's offical ,

Filtering for User Picker (multiple fields) custom fields will be available to everyone by the end of next week (28th Feb). 

Will share an update once it is 100% released, 

Have a great weekend, 

Saskia

53214b82d75d ,

Our customer uses many user-picker type customfied in their sites. 

Do you have any method to invetigate if default value are configured for all user-picker type customfields?

And do you have any method to update default values for those user-pickers as bulk? 

53214b82d75d when you say soon can you give a date estimate roughly on this thank you

Hey everyone,

We’re excited to announce that we will soon be rolling out filtering for the User Picker (multiple users) custom field in Jira.

Important announcement: We have also added validation that prevents the User Picker (multiple users) custom field from being saved if the user is no longer inactive, where a filter is enabled on the custom field context.

N.B. This change reflects validation in User Picker (single users) custom fields.

Examples where this may be a problem:

• If the default value of your User Picker (multiple users) custom field is inactive, you won’t be able to create an issue without changing the default value to an active user.
• If you apply a filter, but the default value of the User Picker (multiple users) is not an allowed value after the filter is applied, you won’t be able to create the issue.

We recommend that you check your User Picker (multiple users) custom fields now, so that once this functionality is available, there is no disruption to issue creation.

To locate default value configuration of User Picker (multiple users) custom fields:

Navigate to ⚙️ > Issues > Custom fields > [locate your User Picker (multiple users) custom field] > … > Contexts and default value > Default value. Check that your default value is not set to an inactive user. 

See below, for what it should look like:

If you have any questions, please do not hesitate to reach out,

Saskia van der Peet,

Product Manager, Jira

svanderpeet@atlassian.com

We just realised that when migrating from Jira server to cloud, a custom multi user picker with filtering, the filtering is migrated, and still applies, but because of the above we have no way to modify or remove it.. 

This is problematic..

I know that this is being rolled out for user picker (single and multiple) custom fields here, but hoping that doing this for group pickers is not too far along on the roadmap? This is really hindering a lot of our workflows

684cb16ed833

I see that this issue's status is now In Progress. Is there an anticipated Release Date?

Now that this is coming... this is only on custom fields? So it couldn't be applied to the Assigned To field?

Hello,
looking forward seeing this feature ASAP.
I wonder after releasing it, we will be able to use it with system fields like "request participants". won't we?