jira cloud jql query (with python) no issue found today

[Aurelie reberac]

I run a python script which retrieves tickets on my jira cloud instance. While it wads working very well yesterday and the days before, this morning no tickets found ? Is there an issue today with Jira cloud ?

thanks for your help

[Aron Gombas _Midori_ · Accepted solution]

If:

• your JQL when running that through the web interface returns the expected result
• and you have not changed the code

...but suddenly it doesn't return anything, then my tip would be checking the authentication part.

Isn't this possible that you are using an API token which disallows seeing the issues you expected? (Because that belongs to another user account and that user account has no access to the corresponding Jira spaces, for example.)

[Arkadiusz Wroblewski]

Hello and welcome to the Community @Aurelie reberac 

Can you share the exact JQL and the exact API response you get back? Without that, it is hard to tell whether the problem is in the query itself, the Python call, or the result handling.

Also, if your JQL uses date functions like now() or startOfDay(), then today’s time change could absolutely be relevant. Jira Cloud supports those date functions, and in Germany/Berlin the clocks moved forward by one hour on March 29, 2026. 

The first thing I would do is run the same JQL directly in Jira advanced search and compare that result with what your Python script returns. If the UI shows issues but Python does not, then the next useful detail would be the exact request code and the response body.

[Trudy Claspill]

Hello @Aurelie reberac 

Welcome to the Atlassian community.

Adding to this, if you ever wonder if there is a widespread incident affecting multiple Atlassian Cloud products you can check their status page.

https://status.atlassian.com/

And often when there is an incident you will see multiple reports of the related problem appearing in the relevant community forums.

[Aurelie reberac]

Hello,

@Arkadiusz Wroblewski it works well in JIRA Advanced Search...

Then I saw the comment of @Aron Gombas _Midori_ ...and by changing the API token it works ! The one previously used belongs to another user account and it may expire...

Thanks both for your help ! 

[Arkadiusz Wroblewski]

@Aurelie reberac Well it mostly typically 2 Things.

Changes on endpoint or lack of access when something suddenly stops working.

Great it working again.

[Aron Gombas _Midori_]

@Aurelie reberac Glad that it was helpful. Please accept my solution so that it will help others in the future, too.

[Aurelie reberac]

Hello, and thanks for your answers.

@Arkadiusz Wroblewski , My JQL query is very simple :

jql_request = 'issuetype in ("EUV Observation config", "FUV Observation config", "NUV Observation config", ' \
        '"Scanner Check config", "XUV Check config", "Warmup EUV 1kV", "Warmup FUV 1kV") AND status in (SENT, "🟪 EXECUTED", "🟫 CANCELED", "🟥 NOK", "🟨 POK", "🟩 OK") ORDER BY cf[10053] ASC, cf[10279] ASC, created DESC'

I'm looking for tickets with a specific issuetype and specific status (possible values for issuetype and status are in given in a "list". 

I used enhanced_jql as I have something like 500 tickets. 

# first read all pages and collect issues
all_issues = []
isLast = False
nextPageToken = None

while not isLast:
    response = jira_wf.jira.enhanced_jql(jql_request, nextPageToken=nextPageToken )
    all_issues.extend(response.get('issues'))
    isLast = response.get('isLast')
    if not isLast:
        nextPageToken = response.get('nextPageToken')

 Yesterday it was working well, today, "all_issues" is empty...

[Arkadiusz Wroblewski]

@Aurelie reberac 

The JQL itself looks fine to me, so my next check would be very simple: does this exact same JQL still return issues in Jira Advanced Search?

If yes, then I would look less at the JQL and more at the Python / enhanced_jql response. Atlassian’s newer /search/jql endpoints do use nextPageToken, and the older /search endpoints are being removed, but I do not see an obvious “today this endpoint changed” notice in the current Jira Cloud changelog. 

So please check:

1. the full first raw response, not only response.get('issues')
2. whether there is any error/warning/message in that payload
3. and whether the same JQL still works in the Jira UI

If the UI returns issues but your wrapper returns an empty issues array, then I would suspect the API wrapper / response handling before I would suspect the JQL itself. Atlassian also documents that /search/jql is eventually consistent, but that usually matters more for very recent updates than for a stable query like yours.

Without More Tests on your side we speculating more.

https://community.developer.atlassian.com/t/rfc-127-jira-software-cloud-api-changes-improving-scalability-for-software-space-issue-results/98871