Forums

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

Jira API: Ranking changes not immediately reflected in JQL search results

Illia Drachuk
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!
May 1, 2026

Hi everyone,

We’ve noticed a delay when updating and retrieving issue rankings via the API.

Specifically, after calling rest/agile/1.0/issue/rank to change an issue’s rank and receiving a successful response, we immediately call rest/api/3/search/jql to fetch the updated list of issues ordered by rank. However, the updated ranking is not reflected right away. It typically takes around 3–5 seconds before the ranking changes appear in the query results.

Is this expected behavior? If so, is there a recommended way to ensure we retrieve the updated ranking immediately after making the change?

Thanks in advance for your help.

1 answer

0 votes
Gor Greyan
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.
May 1, 2026

Hi @Illia Drachuk

Thanks for the question.

When you update ranking via the Agile API rest/agile/1.0/issue/rank,  the change is applied immediately for Agile views. However, JQL search relies on Jira’s search index, which is eventually consistent in Cloud.

That is why there can be a short delay before the updated ranking is reflected in JQL results.

It’s a known characteristic of Jira Cloud search that updates are processed first and then propagated to the index asynchronously.

My suggestion is to add a small delay before querying it back.

 

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events