nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Jira API - Not pulling most recent tickets

Chris Anderson_c8ybit

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

Accepted answers

Enric Font_9rmi2h

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.

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

project = CS ORDER BY updated ASC

All comments

Enric Font_9rmi2h

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.

<strong>project = CS</strong> 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_c8ybit

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_c8ybit

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.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud

jira-api