Forums

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

Empty Issues Returned in the API response having filters

MQSquids March 26, 2025

I'm trying to fetch the issues for multiple projects using the Updated datetime filters. I was able to query the data programmatically using this request uri until yesterday but something changed between 3/25 past noon and the same query is returning null content. 

Here is the response with query details -  

{Method: GET, RequestUri: 'https://xxxx.atlassian.net/rest/api/2/search?maxResults=50&expand=changelog&validateQuery=true&jql=updated >= '2025-03-24 10:00' AND updated < '2025-03-24 10:06'', Version: 1.1, Content: <null>.

Appreciate very much if someone can help troubleshoot. 

Thanks,

 

1 answer

1 vote
Trudy Claspill
Community Champion
March 26, 2025

Hello @MQSquids 

Welcome to the Atlassian community.

If you run the same JQL in the UI do you get results? I suspect not.

The Updated timestamp is the last time that the issue was updated. I suspect that all the issues that filter returned previously have been updated again, and the Updated timestamp is no longer within the 6 minute window you specified.

MQSquids April 2, 2025

Appreciate the response, Trudy. 

I did run the query in the UI and it was returning few results. It started working after I commented the startAt parameter under the search REST API having maxResults = 50. However, this might work until the search results stay within 50 (max allowed) rows for issues. Is there a better way to handle this if I need to scale beyond 50 rows for issues updated within every 5 mins.

Context: My ingestion service hits the search API to fetch issues updated in every 5 mins window. Currently maxResults are set to 50.

Suggest an answer

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

Atlassian Community Events