Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

sprint in closedsprints() is not working

sprint in closedsprints() is not working.  all other functions (futuresprints, opensprints etc.,) are working fine.  Is this a known issue?

1 answer

1 accepted

0 votes
Answer accepted
carlosughini Community Leader Feb 04, 2020

Hello Raghu,

My apologies for this inconvenience that you are facing, I really understand how frustrating this can be.

First of all, could you confirm if you have a closed sprint? 

It is important to note that this function searches for issues that are assigned to a completed Sprint.

This is in contrast to openSprints() which finds issues in sprints that have not yet been completed.

Give a try and in case you still face any errors, please provide us with some more information like an image of your completed sprint and of the query that you are executing.

Looking forward to hearing from you.


Carlos Henrique Ughini

Hi Carlos, 

I am also facing the same issue in our organization. we do have so many closed sprints but we are getting the following error, when we ran "sprint in closedSprints()".



carlosughini Community Leader Feb 19, 2020

Hello Akhil,


I'm thinking that maybe you've been affected by the following bug:



Could you please check the link above?



Suggest an answer

Log in or Sign up to answer

Atlassian Community Events