Forums

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

New API only returns {"issues":[],"isLast":true}

Darryl Hilton
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
October 15, 2025

Hi

Before I start I am not an expert on this, we had a process set up by a former colleague which had always worked until recently. I believe it is due to the deprication of the old API. I updated the proces to point to:

https://api.atlassian.com/ex/jira/$(JIRACLOUDID)/rest/api/3/search/jql

instead of 

https://api.atlassian.com/ex/jira/$(JIRACLOUDID)/rest/api/latest/search

I am using a HTTPCaller in FME for those familiar that looks like below, although the issue I am getting is also the case in Postman.

Every query now only returns a response body of

{"issues":[],"isLast":true}

This is regardless of what parameters I include or not. If I just have a project parameter such as:

https://api.atlassian.com/ex/jira/$(JIRACLOUDID)/rest/api/3/search/jql?jql=project=12200

it does the same, in fact it desn't matter what I put as the project ID (00000 would still do the same)



Screenshot 2025-10-15 153152.png

Full URL for ease of reading:

https://api.atlassian.com/ex/jira/$(JIRACLOUDID)/rest/api/3/search/jql?expand=@Value(_query_expand)&jql=@Value(_query_jql)&maxResults=@Value(_max_results)&validateQuery=@Value(_query_validateQuery)

example:

https://api.atlassian.com/ex/jira/$(JIRACLOUDID)/rest/api/3/search/jql?jql=project=12614 AND updated>=2025-10-14&expand=changelog&maxResults=1000&validateQuery=warn

 

All the parameters are the same as the old, succesful API version

Any assistance would be gratefully received

 

1 answer

1 accepted

0 votes
Answer accepted
Jack Dillon - Pallas Apps
Atlassian Partner
October 15, 2025

Hey @Darryl Hilton 

 

Try querying your atlassian site followed by "/rest/api/3/search/jql?jql=" then you jql. For example:

https://myAtlasSite.atlassian.net/rest/api/3/search/jql?jql=project=ABC&fields=*all

This is the way I use to query that search jql endpoint that you are using and it works for me. Let me know if this way doesn't work for you.

 

Best,
Jack

Darryl Hilton
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
October 21, 2025

Thanks for this Jack

It turns out it was partially user error on my part as so ome my project codes were unusued so I thought nothing was returning, I have found some active project codes that do return results.

I still needed to use my https://api.atlassian.com/ex/jira/$(JIRACLOUDID)/rest/api rather than https://myAtlasSite.atlassian.net/rest/api to get data back.

However including Fields=*all as you suggested made the process a lot easier form that point, so thank you

Suggest an answer

Log in or Sign up to answer