It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

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

Josh Ramdhan Jul 14, 2016

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 for this post are closed

Community moderators have prevented the ability to post new answers.

Post a new question

0 votes
Tom Proctor Jul 14, 2016

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

 

Kirsten Manica Dec 28, 2016

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 Feb 06, 2017

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

Kirsten Manica Feb 06, 2017

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.

Andrew Heinzer Atlassian Team Jul 06, 2017

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

Like Sarah Chui likes this
Kirsten Manica Jul 06, 2017

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

0 votes
JamieA Jul 19, 2016

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 Apr 28, 2017

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 Jul 09, 2017

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.

This widget could not be displayed.
This widget could not be displayed.
Community showcase
Published in Next-gen

Introducing subtasks for breaking down work in next-gen projects

Teams break work down in order to help simplify complex tasks. This is often done iteratively, with tasks being broken down into smaller tasks and so on until the work is accurately captured in well-...

1,095 views 13 15
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you