querying sprint issues gets different results


I'm trying to build an App that shows all the issues in a sprint plus sone extra issues. While researching for the best way to request the issues I found, that different queries deliver different results

1. using the agile-API:


gets 24 issues in the sprint.This result looks Ok


2. using search-API


gets 50 issues out of 28450 total

this is definitely wrong


3. using the standard search with the same JQL query

.../issues/?jql=sprint %3D 754

finds 23 issues


which result is right and how can I tweak the second (search via rest API) to deliver the correct result?


3 answers

0 votes
Warren Levy Community Champion Sep 05, 2017

Hi Hartmut

Is it just a typo that 1. has 745 and 2. and 3. have 754?

0 votes
Warren Levy Community Champion Sep 05, 2017

Okay, part of an answer for you ...

The parameter you're using in 2. is wrong, so it's ignoring it and returning everything! Its just jql not jqlQuery, so it should be


Looking again at 3., I'm not sure what that call is, but if you make the change to 2. as I've stated above, it should agree with 1.

Hope this helps


I think in 3, Hartmut means that "sprint = 754" has been typed into the search box in the UI.  It should return the same as 1 (and your corrected 2), but if it does not, then we should compare the different results to have a look at the issue that appears in one search and not the other.

Warren Levy Community Champion Sep 05, 2017

Hi Nic

You're probably correct, I was confused by the .../issues/?jql= bit of 3.

Just typing Sprint=xxx into the Issues search returns exactly the same number for me, so that would mean that I'm getting all three returning the same number of issues.

@Hartmut Boekhoff, over to you now

Thanks Warren!

the *jql* parameter did the trick.

With that correction, I get 24 issues from the first and 33 from the second and third request. But those are numbers I can deal with.


Many thanks again,


Suggest an answer

Log in or Sign up to answer
Community showcase
Published Feb 26, 2019 in Jira Software

How to prevent the propagation of unused project schemes, workflows & screens in Jira software

Atlassian ranks project attributes as the third most important factor impacting performance in the category of data. It’s not surprising, since project attributes are precisely the rules used to ma...

586 views 0 6
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you