nextPageToken is not included in last page of results of the "Search for issues using JQL enhanced search (GET)" endpoint

XMLWordPrintable

    • 1
    • Severity 2 - Major

      Issue Summary

      nextPageToken is not included in last page of results of the "Search for issues using JQL enhanced search (GET)" endpoint.

      The documentation indicates:

      nextPageToken string
       
      The token for a page to fetch that is not the first page. The first page has a nextPageToken of null. Use the nextPageToken to fetch the next page of issues.

      Steps to Reproduce

      Make any web request to the /rest/api/3/search/jql endpoint, ensuring the JQL will return less than the default 50 results (or less than whatever value the maxResults is indicating).

      Expected Results

      The nextPageToken key is null for the last page of results.

      Actual Results

      There is no nextPageToken ** key on the last page of results. The key only appears when it has a value in it. According to the documentation, it should be included with a null value.

      Workaround

      Currently there is no known workaround for this behavior. A workaround will be added here when available

            Assignee:
            Purushotam Agrawal
            Reporter:
            Rene C. [Atlassian Support] (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: