Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Jira API - Not pulling most recent tickets

Chris Anderson
April 20, 2026

Hi

 

We have been using the Jira rest API to pull down the data on tickets (on a nightly schedule) using the following GET call:

https://COMPANYNAME.atlassian.net/rest/api/3/search/jql?jql=project%20%3D%20CS&fields=*navigable

 

The issue we have is that every Monday morning we only get our tickets created up to Saturday the previous week. It's as if the data is not refreshed since Saturday night and its causing an issue with our internal reporting.  From Tuesday onwards it seems fine and we then get the previous day's tickets come through fine on the overnight call.

We have been downloading from the above API for several years now and it has only become an issue in the last 2 weeks on Monday's only.  Does anyone have any ideas as to what could be going on?

 

Kind Regards

 

Chris

1 answer

1 accepted

0 votes
Answer accepted
Enric Font
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
April 20, 2026

Dear @Chris Anderson 

If you are only calling the endpoint once and not following nextPageToken, you may be silently missing part of the project’s issues. The API documents pagination for this endpoint.

project = CS by itself does not protect you from changing result order. For reporting pulls, use something deterministic such as:

project = CS ORDER BY updated ASC

 

Chris Anderson
April 20, 2026

Hi Enric, Thanks for the response. 

I am already feeding the "nexPageToken" through into subsequent calls in order to pull the full data set.  However I currently do not explicitly set an ORDER BY for any field, so will add that in based on updated datetime and see if that helps.

I will let you know either way if it works

 

Kind Regards

 

Chris

Chris Anderson
April 20, 2026

Hi  @Enric Font  adding the order by clause into the JSQL query seems to have worked and I am now getting the latest tickets pulling. I cannot 100% confirm whether it was the  code change or the fact that the data is now available through the API, but my gut tells me that it did make the difference.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS
AUG Leaders

Atlassian Community Events