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

search issues that were not closed and moved to another sprint

I want to search for issues that were not completed and moved to another sprint. I know I can open reports of past sprints where I can see issues that were completed and those that weren't, but I don't want to go through each project and look at reports.

Is there a way to do this using jql in the issues tab search.


3 answers

1 accepted

3 votes
Answer accepted

Hi Anas,

Unfortunately, there's no native JQL function to get issues that were not completed in a sprint and later added to a new one.

Assuming you were only interested in issues that belonged to a sprint at the very same moment of the sprint closure, and not in issues removed from a sprint after it had already started, then issues belonging to more than one sprint should kindo-of meet the requirement you are looking for.

The following workaround might help by saving some time:

  1. Go to the issue navigator and execute this query: Sprint is not EMPTY
  2. Set the Issue Key and the Sprint fields as the only columns to be shown.
  3. Export the results to CSV (current fields only) setting the semicolon character (;) as a separator.
  4. Open the resulting CSV file with Excel and filter data to hide rows with no value in the second occurrence of a column with the Sprint header. At this point, only issues belonging to at least two sprints ahould be shown.
  5. Create a comma-separated list of issue keys resulting from step 4 and paste it in this JQL: issuekey in (<your  comma-separated list of issue keys>)

Should step 1's filter return the maximum number of issues set (typically 1000 issues) you might need to add anything else to said filter in order to get a different set of issues.

Hope it helps.

Thank you so much Ignacio, the steps above did exactly what I was looking for!

Like Ignacio Pulgar likes this

Glad to help! :)


Thanks @Ignacio Pulgar this was very helpful

Like Ignacio Pulgar likes this

Hello Anas,

the default JQL functions don't have such options but there are a few apps that can help you:

Please note that there are currently a few restrictions in ScriptRunners JQL functions with regard to sprints.

Thanks a lot.

But this isn't exactly what I was looking for, as this returns issues that were moved between projects. I'm looking for issues that were not completed by sprint end, regardless of sprint.

Suggest an answer

Log in or Sign up to answer