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

Query to find issues which previously belong to a sprint

Dear All,

I am looking to query issues which were previously tagged to a sprint, and now moved to new sprint. Like I had issue ABC-1 which was in sprint 1 (among other issues). I moved this to Sprint 2. How can i write query to find all the issues which got moved from Sprint 1.


Sprint field doesn't support WAS operator. Using Script Runner or any other plugin is not an option.

3 answers

1 vote

Hello @Ashish Sharma

You can achieve your requirement easily using this JQL query (no need of plugin)

Sprint in closedSprints() and (Sprint in openSprints() or Sprint in futureSprints()) and type not in (Sub-task)

Here you get issues which had sprint field in closedSprints() i..e old sprints and are also present in the open or future sprints  which means issues have been part of earlier closed sprints and are now part of active/future sprints. 

You can add criteria like Project = ABC etc to further filter your search results.

Hi @Tarun Sapra, Perheps I was not clear enough. I am afraid this query won't work because:

Issue was moved to Next/Future sprint BEFORE the current sprint was completed hence such issues will not be part of the result set returned by query "Sprint in closedSprints()".




Then I would suggest you to try the JQL functions which are part of the ScriptRunner plugin





These might come in handy since you have removed your issue from the current "started" sprint and moved to next sprint thus above JQL functions should give you the right results. But since you have shared that ScriptRunner is not an option then I don't think you can achieve what you want. 


There should be a "WAS" operator for "Sprint" field also.

Like # people like this
Tarun Sapra Community Leader Aug 16, 2018

Actually was operator is not required because we have "closedSprint()" which does the job well, but in your case it's a specific scenario wherein you have taken the issue out of an open/active sprint hence closedSprint() is not working for you. So i feel a plugin is  a way to go for this as Atlassian can't always prioritize such edge case requests.

This is not an edge case! WAS operator IS required!

Teams and product owners who constantly manage the scope of the sprint, may (and should) descope issues from the sprint, which they decide that they are not going to do for various reasons. By doing this they are actually changing the sprint plan. Later on, we want to see which issues were previously assigned to the previous - in order to analyze the impact on the overall plan.


Please add WAS operator....

Like # people like this

try this

issueFunction in removedAfterSprintStart("Sample Scrum Board", "Sample Sprint 3")

However, it doesn't look like removedAfterSprintStart is available for JIRA Cloud. Is there any other workaround?

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events