Create a quick filter query to show issues added to current sprint after sprint start date.

I want to create a query in the quick filters to show me all issues added to the current sprint (i.e. the sprint name isn't hard coded into the query) after the sprint was started.  The use for this is to determine how our sprint scope is changing from the beginning to end.

I found an article that suggested that I use fixVersion, but our organization doesn't utilize this feature, which renders this useless.  The article also suggested hard coding the sprint name into the query, which also isn't what I'm looking for.

In pseudo-code, the query be something along the lines of:

SHOWIF date_added_to_sprint > sprint_start_date

I'm very new to JIRA and SCRUM so any help would be much appreciated.

2 answers

Comments Closed

There is a Sprint Report that will show you issues added to a Sprint and other good things. Check here for details;


Tom ~ If I'm correct, this report is great after you've completed the Sprint, but not when it is an active Sprint. I, like Josh, would love to know how to view the scope creep on an active Sprint. Any further help outside of something like scriptrunner?

Kirsten, Josh - found a solution yet? Having the same problem here

Hi Hanna!

No, unfortunately. I definitely use, and love, the Sprint Reports that Tom mentioned- the after-the-fact data. But no, I haven't found a solution to getting a view into what has crept in while the Sprint is in session.

You could try to look at the Burndown report to see what issues might have been added to the sprint after the start.  These would be registed as a scope change event in this report and you can see this even when the sprint is active.

Andrew ~ THANK YOU. It seems so obvious now that I'm looking at it. 

0 votes

If you have SciptRunner you can use You have to put in the board name, but not the sprint name.


Is there is way to not hardcode the board name and sprint name so the user doesn't need to change it every single new sprint. Thanks

The sprint name is optional. The board name is not however. At least at one point in time, issues could be on multiple boards, so it may have been added after the start of the sprint on one board but not on another.

Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

2,781 views 11 18
Join discussion

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
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot