Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-79155

User Picker Search capped at 100 users

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Medium Medium
    • None
    • 10.3.12, 11.1.1
    • None

      UserPickerBrowser only shows up to 100 users when filtering by a group, even through the group has more than 100 users.

       

      Issue Summary

      When opening the UserPickerBrowser window (for example, from Watchers or any other screen that uses user filtering), filtering only by group displays a maximum of 100 users, even if the group contains more. As a result, customers are unable to find users beyond that limit, since they never appear in the search results. This issue disrupts customer workflows, particularly when assigning watchers or performing similar user-selection tasks.

      Steps to Reproduce

      1. Create a group call Group A
      2. Create more than 101 users to Jira
      3. Add those users to Group A
      4. Go to any issues -> Watchers
      5. Click to Browser users.
      6. Filter by Group A

      Expected Results

      We expected to see all users in the search result

      Actual Results

      We’re only able to see up to 100 users.

      Customer Impact

      This issue has a significant impact on customers with large user groups. Currently, there is no way to access or select users beyond the 100-user limit when filtering by group. This limitation blocks critical workflows such as assigning watchers, sharing issues, or selecting users for notifications—particularly in organisations with large teams or departments. As a result, customers are unable to complete essential tasks, leading to frustration and workflow delays.

      It’s worth noting that in version 9, the particular customer that raised this issue used this feature extensively without experiencing performance issues, even with groups containing a large number of users.

       

      Workaround

      Currently there is no known workaround for this behaviour. A workaround will be added here when available

              Unassigned Unassigned
              b1328cf7ff67 Marcos Sousa
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: