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

User filtering (single user picker) does not work in the new issue view

      Summary

      In New issue view single user-picker custom field does not apply the group filtering configured for the field.

      Steps to Reproduce

      1. Create a single user picker custom field by accessing Jira Settings > Issues > Custom field > Add custom field.
      2. Add that custom field to a screen.
      3. Access that's custom field setting page and setup group/filter to a group with few users in it.
      4. Go to the project where that screen is placed and with the new issue view enabled, try to edit that custom field option.

      Expected Results

      The only users are shown are in the filter/group configured for the field.

      Actual Results

      All users are displayed.

      Notes

      The User picker custom field literally displays ALL users including Portal customers from Jira Service Desk.

      Workaround (may not be applicable for some sites as we move to the new issue view)

      • Disable the new issue view. For that follow the steps below:
        1. Select your avatar and choose Profile
        2. Turn off the New Jira issue view toggle under Labs

            [JRACLOUD-81820] User filtering (single user picker) does not work in the new issue view

            This is a needed functionality - we have been asked multiple times by our clients to implement user filtering on user single and multi-select types of fields.

            Tomislav Tobijas (Koios) added a comment - This is a needed functionality - we have been asked multiple times by our clients to implement user filtering on user single and multi-select types of fields.

            Any Updates on this?

            NN22JAMOAKO added a comment - Any Updates on this?

            Atlassian Update - January 2023

            As I have not received any responses to this comment I am closing this ticket.

            If you disagree with the closing of this ticket, please add a comment here saying why and we can reopen it.

            Anusha Rutnam added a comment - Atlassian Update - January 2023 As I have not received any responses to this comment I am closing this ticket. If you disagree with the closing of this ticket, please add a comment here saying why and we can reopen it.

            Are the watchers of this issue still able to reproduce the problem? I am unable to on my Cloud instance - only members of the group I have limited the User Picker (single user) custom field to appear in the dropdown, in the new issue view.

            Anusha Rutnam added a comment - Are the watchers of this issue still able to reproduce the problem? I am unable to on my Cloud instance - only members of the group I have limited the User Picker (single user) custom field to appear in the dropdown, in the new issue view.

            Ash Green added a comment -

            This should be marked as critical. This is a shop stopper for our business. This is a bug, not a new feature request. How can it just be dismissed??
            I'm quickly losing patience with Atlassian, just dismissing critical issues. 
            If I treated our customers in this way, we'd have no customers.

            Ash Green added a comment - This should be marked as critical. This is a shop stopper for our business. This is a bug, not a new feature request. How can it just be dismissed?? I'm quickly losing patience with Atlassian, just dismissing critical issues.  If I treated our customers in this way, we'd have no customers.

            The workaround isn't valid since it's not possible to "Turn off the New Jira issue view toggle under Labs".

            Please update the workaround or fix this issue

            Italo.Lobato added a comment - The workaround isn't valid since it's not possible to "Turn off the New Jira issue view toggle under Labs". Please update the workaround or fix this issue

            Megha added a comment -
            Atlassian Update - October 26, 2020

            Hi everyone,

            Thank you for previously raising this bug and bringing it to our attention.

            Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved. To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Jira users.

            As we continue to roll out features we do look at requests made by our users and if you feel like this bug is still impacting your team please let us know.

            Thank you again for providing valuable feedback to our team!
            Jira Cloud team

            Megha added a comment - Atlassian Update - October 26, 2020 Hi everyone, Thank you for previously raising this bug and bringing it to our attention. Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved. To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Jira users. As we continue to roll out features we do look at requests made by our users and if you feel like this bug is still impacting your team please let us know. Thank you again for providing valuable feedback to our team! Jira Cloud team

            Given that the option to use the old view workaround may disappear at any time, we're trying to train our users not to use it. Hoping this gets fixed very soon.

            Esther Strom added a comment - Given that the option to use the old view workaround may disappear at any time, we're trying to train our users not to use it. Hoping this gets fixed very soon.

              Unassigned Unassigned
              akhan@atlassian.com Asim K
              Affected customers:
              23 This affects my team
              Watchers:
              35 Start watching this issue

                Created:
                Updated:
                Resolved: