-
Bug
-
Resolution: Fixed
-
Low
-
6.4.10, 7.2.7, 7.4.0, 7.3.3, 7.10.0, 7.9.2, 8.2.2, 7.13.9, 8.5.0, 8.5.3, 8.5.5
-
6.04
-
19
-
Severity 2 - Major
-
42
-
Summary
The user search result is truncated to the first 1000 users on the instance. For example: with parameters &startAt=0&maxResults=1000 we get the first 1,000 users but setting &startAt=1001 results in no users being returned. Using startAt=600, we only have 400 users returned.
Environment
- JIRA 7.3.3 or latest
Steps to Reproduce
- Create 1,300 user in JIRA
- Send a GET HTTP request to the endpoint <JIRA-Base-URL>/rest/api/2/user/search?username=.&includeInactive=false&startAt=1001&maxResults=1000
Expected Results
Return user 1001-1300 in the list
Actual Results
No users are returned.
Workaround
If you exclusively require the use of REST API
You may stream users in batches based on a wildcard search for the string provided. For example, the following call will return the following test elements:
- email= test123@gmail.com or email= 123email@gmail.com
- username = ab123 or username= 123ab
- displayname = ab123 or displayname= 123ab
If any of those have more than 1000 results, search for 'aa', 'ab', etc...
If it's feasible to query the database
You may retrieve similar information by querying the cwd_user table in JIRA's database.
- is caused by
-
JRASERVER-70269 DefaultUserPickerSearchService doesn't allow unlimited search
- Closed
- is duplicated by
-
JRASERVER-64343 Unable to Search User from Number 1000 and above using REST API
- Closed
- relates to
-
JRASERVER-63771 User picker "in group" filter does not display all users when having more than 1.000 users in JIRA.
- Closed