Inactive users will no longer be valid values of the User Picker (multiple users) custom fields

[#1]

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. Related request: JRACLOUD-40963 

This means you will be able to filter which users are allowed values of a User Picker (multiple users) custom field, by adding Groups and/or Project Roles to the filter. This is the same as how you configure filters for the User Picker (single user) custom fields.

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

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

This may be a problem when the default value of your User Picker (multiple users) custom field is set to an inactive user, and you have a filter enabled for the custom field. As a result, you won’t be able to create an issue without changing the value of the field to an active user.

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. 

If the default value is set as an inactive user, either remove the default value, or update it to be an active user. Alternatively, you can disable the filter for that custom field.

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

[Yatish Madhav]

This is amazing! Thank you @Saskia and Atlassian!

[Lior Pinelis]

@Saskia It is great to have an option to filter, but it is also a step back.

It is going directly against what people have been asking for since 2015 in JRASERVER-59132 .

We have run into this issue multiple times, where we needed for a user select field to be able to select an inactive user, or when an inactive user on an old ticket needed to be copied via automation into a new ticket as part of an automation process (it was in an HR related activities), and the change to the Multi select, just makes this issue worst.

Hope Atlassian team will reconsider and allow for Inactive Users to be selected, and if needed to be removed by using filter option. That would be a much better way to handle this situation. 

[Yatish Madhav]

@Saskia Can you post an image of what it will look like with the project role and user group filtering?

The image above is only for the default value, issue type and project scopes - right? Or am I missing something?

Also, how will i know when this is rolled out on our instance?

Thank you

Yatish

[Saskia]

@Yatish Madhav Yep absolutely, I hadn't added an image there, so as to not cause confusion prior to its release. 

It will look exactly like the User Picker (single user) filter, but see below for the filter on a User Picker (multiple users) custom field.

We will let you know on this post, and on JRACLOUD-4093 once we update the status of the ticket as well.

Below is the filtering on a 

 

[Yatish Madhav]

Great - thanks for that @Saskia - Looking forward to it!

[Michael diLorenzo]

When do you plan on discontinuing the process of billing for inactive users?