Uploaded image for project: 'Jira Service Management Cloud'
  1. Jira Service Management Cloud
  2. JSDCLOUD-4187

Inconsistent JIRA Service Desk REST API Pagination

    XMLWordPrintable

Details

    • Bug
    • Resolution: Fixed
    • Low
    • Forge and Connect
    • None

    Description

      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

      1. Create a GET request for Customer Requests
        <baseURL>/rest/api-name/resource-name?start=0&limit=10
        
      2. Observe the "size" from the result
        Results
          "size": 76,
          "start": 0,
          "limit": 100,
          "isLastPage": true,
        
      3. Change the start to a higher value and re-send the GET request
      4. <baseURL>/rest/servicedeskapi/request?start=20&limit=100
        
      5. Observe the "size" from the result
        Results
          "size": 36,
          "start": 20,
          "limit": 100,
          "isLastPage": true,
        
      6. Change the start to a higher value and re-send the GET request
      7. <baseURL>/rest/servicedeskapi/request?start=30&limit=100
        
      8. 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

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              cchan Chung Park Chan
              Votes:
              3 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: