Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-40963

Allow user filtering for User Picker (multiple users) custom field type

XMLWordPrintable

    • 1,855
    • 140
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

    • Hide

      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.

      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

      Show
      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. 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

      NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.

      The User Picker (single user) custom field type allows you to limit the set of users available in your user picker field to specific groups or project roles. Limit number of users for user picker fields.

      UserPicker(single-user).snagx

      The User Picker (multiple users) custom field type doesn't have this option available.

      UserPicker(multiple-users).snagx

      Workaround

      There is no known workaround exists to limit users available in a User Picker (multiple users) custom field type.

              684cb16ed833 Carol Low
              4d69c81d15f7 Tomasz Stec
              Votes:
              609 Vote for this issue
              Watchers:
              307 Start watching this issue

                Created:
                Updated: