Max 100 records when we do API calls against the Cloud jira project. Previously it was 1000

[milan.shah]

We are on Cloud.

This was working previously.

Seems like there is a limit on server, https://confluence.atlassian.com/adminjiraserver071/limiting-the-number-of-issues-returned-from-a-search-view-such-as-an-rss-feed-802593125.html?_ga=2.108740480.387327035.1593686919-1576342130.1593686919

But how do I fix this for Jira Cloud.

[milan.shah]

the default value for cloud services is still 1000 (according to documentation)...so I am wondering why my stuff is now failing.

I will look into the above two suggestions.

[Warren]

Hi @milan_shah 

This changed about 2 years ago.

You will need to pass in the parameter startAt, which you can see in the returned json after any API call. By default it will be 0.

So after your first API call, you do the same call again but pass in startAt=50, then the next call will be startAt=100 etc. You would need to do this until the startAt value is greater than the value total returned in the json.

Hope this helps and is clear.

[Phill Fox]

Hi @milan_shah 

The first thing I would try in the pagination options. (https://developer.atlassian.com/cloud/jira/software/rest/)

In particular you need to consider these two options

• maxResults
• startAt

So to retrieve the issues from 101 to 300 your request would look similar to this

http://host:port/context/rest/api-name/api-version/resource-name?startAt=101&maxResults=200

You can of course try just increasing the maxResults on its own but I would be wary of doing this as it can lead to performance issues for your instance.

Phill