-
Type:
Bug
-
Resolution: Not a bug
-
Priority:
Low
-
Component/s: Work Item - Search - Backend - JSIS
-
None
-
1
-
Severity 2 - Major
Issue Summary
maxResults for Search for issues using JQL enhanced search (GET) does not work as indicated in the documentation
The documentation indicates:
maxResults integer
The maximum number of items to return per page. To manage page size, API may return fewer items per page where a large number of fields are requested. The greatest number of items returned per page is achieved when requesting id or key only. It returns max 5000 issues.
Default: 50 Format: int32
Steps to Reproduce
Make a web request to the endpoint /rest/api/3/search/jql ensuring that the JQL returns a large number of issues (1,000+), including the maxResults to something large, like 1,000, while selecting only the ID or key field to maximize the number of results as per documentation. For example:
https://rchiquete.atlassian.net/rest/api/3/search/jql?jql=created%20>%3D%20-300d&fields="issuekey"&maxResults=1000
Expected Results
Up to 5,000 results are received per page.
Actual Results
The maximum results are always capped at 100
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available
- is related to
-
JRACLOUD-92184 nextPageToken is not included in last page of results of the "Search for issues using JQL enhanced search (GET)" endpoint
-
- Closed
-