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

[Josh Ramdhan]

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.

[JamieA]

If you have SciptRunner you can use https://scriptrunner.adaptavist.com/latest/jira/jql-functions.html#_addedaftersprintstart. You have to put in the board name, but not the sprint name.

[Rex Cooper]

Jamie,

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

[JamieA]

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.

[Deleted user]

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

https://confluence.atlassian.com/jirasoftwarecloud/sprint-report-777002722.html

[KirstenManica]

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?

[Hanna Blomqvist]

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

[KirstenManica]

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.

[Andy Heinzer]

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.

https://confluence.atlassian.com/jirasoftwarecloud/burndown-chart-777002653.html

[KirstenManica]

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