maxResults values bigger than 50 are not taken into account when calling /rest/agile/1.0/board REST API endpoint

XMLWordPrintable

    • 1
    • Severity 3 - Minor

      Issue Summary

      When calling the REST API endpoints starting with /rest/agile/1.0/board/ID/sprint the value set for the parameter maxResults is not taken into account if it is bigger than '50' (it always return 50). The parameter startAt works fine instead.

      Environment

      Jira cloud

      (Optional - If Applicable)
      *
      *

      Steps to Reproduce

      1. Call any agile/1.0/board endpoint passing a value for maxResults that is lower than 50
      2. See that this works fine. E.g. https://NAME.atlassian.net/rest/agile/1.0/board/ID/sprint?startAt=20&maxResults=20
        {
          "maxResults": 20,
          "startAt": 20,
          "isLast": false,
          "values": [ .......
        
      3. Call the same endpoint passing a value for maxResults that is bigger than 50. E.g.

      Expected Results

      The maxResults value in the REST response is correctly set to the desired value

      Actual Results

      maxResult is always set to 50

        "maxResults": 50,
        "startAt": 20,
        "isLast": true,
        "values": [.....
      

      Notes

      The same issue reproduces calling:

      • /rest/agile/1.0/board
      • /rest/agile/1.0/board/ID/project
      • /rest/agile/1.0/board/ID/epic
      • /rest/agile/1.0/board/ID/sprint

      (Optional - If Necessary)

      Workaround

      Use the startAt parameter to get all the results

            Assignee:
            Martin Varga
            Reporter:
            Darshan Bargal (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: