-
Bug
-
Resolution: Fixed
-
Low
-
None
-
5
-
Severity 3 - Minor
-
NOTE: This bug report is for JIRA Service Desk Cloud. Using JIRA Service Desk Server? See the corresponding bug report.
Summary
The Pagination used in JIRA Service Desk REST API does not return consistent results
Environment
JIRA Service Desk REST API
Steps to Reproduce
- Create a GET request for Customer Requests
<baseURL>/rest/api-name/resource-name?start=0&limit=10
- Observe the "size" from the result
Results
"size": 76, "start": 0, "limit": 100, "isLastPage": true,
- Change the start to a higher value and re-send the GET request
<baseURL>/rest/servicedeskapi/request?start=20&limit=100
- Observe the "size" from the result
Results
"size": 36, "start": 20, "limit": 100, "isLastPage": true,
- Change the start to a higher value and re-send the GET request
<baseURL>/rest/servicedeskapi/request?start=30&limit=100
- Observe the "size" from the result
Results
"size": 16, "start": 30, "limit": 100, "isLastPage": true,
Expected Results
From the above example, Pagination should return 56 and 46 respectively
Actual Results
Returned values are not 56 and 46 respectively
Notes
JIRA Service Desk REST API is still an experimental release as per this comment
Workaround
No workaround as of now
- is duplicated by
-
JSDCLOUD-8012 REST Api call for customers does not respect pagination (limit, size)
- Closed
- is related to
-
JSDCLOUD-8279 Jira Service Desk REST API pagination attributes not working as expected
- Closed
-
JSDSERVER-4187 Inconsistent JIRA Service Desk REST API Pagination
- Closed
- mentioned in
-
Page Loading...
- relates to
-
SDECO-445 Loading...