API 3 Paging - Accessing issues on key set

[S]

Hi,

I'm using API 3 to query data from Jira Service Management.

https://xxxxxxxx.atlassian.net/rest/api/3/search?jql=project=projectName&startAt=100&maxResults=100

My understating was when I say StartAt = 100 that would mean its key 100 onwards to next 100 but that's not the case...

Is there a way I can query this sequential?

Thanks

[Mehmet A _Bloompeak_ · Accepted solution]

As Joseph mentioned startAt is used for pagination and it has no relation with issue key. As a workaround you can sort issues by key using jql.

https://....atlassian.net/rest/api/3/
search?jql=project%3Dproject%20order%20by%20key&startAt=100&maxResults=100

[S]

thanks @Mehmet A _Bloompeak_ so as I move to next page my startAt will become 200... and so on...

This could be Atlassian's question.. 'Order By' are usually resource intensive operations ... so is should we go for it... In my scenario - its a big pay load.. 100K records!

[Joseph Chung Yin · Accepted solution]

@S -

Based on my understanding, the "startAt" parameter means the 1st 100 rows of your search query returns.  It is not associated with issue key number.

Hope this helps.

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Infrastructure Applications Team

Viasat Inc.

[Joseph Chung Yin]

@S -

If my answer assisted you on your resolution, please click Accept answer when you have a chance.

Best, Joseph