How can I use JIRA to tell how many tickets are completed in the same sprint they are brought into?

[Barney Powell]

Hey folks! 

I'm an Engineering Manager, and I'm trying to debug a squad issue.  We're seeing lots of tickets that are brought in to a sprint that are then rolled-over into the next sprint.

I want to help the squad to understand this, and also provide some metrics they can use to see improvement and progress.

Ideally I'd love a report by assignee that shows how many tickets that were in a sprint when it started were completed in that same sprint (marked as done) against how many tickets have been completed in a different sprint.

I'm not interested in specific sprints, just a time range - so I can demonstrate that we're improving our ability to deliver what we commit to within a sprint.

Many thanks!

Barney

[Ravi Sagar _Sparxsys_]

Hi @Barney Powell 

Try this. This may you get a list of issues where they were part of sprints that are closed but now part of open sprints.

Sprint in closedSprints() and Sprint in openSprints()

Or you can try.

Sprint in closedSprints() and Sprint in futureSprints()

However ideally burndown chart should be referred for more accurate information specific to a sprint.

Ravi

[Alex Ortiz]

Hello,

I recommend you take a look at the burndown chart report.

It might not do exactly what you are asking for, but it will tell you what happened during your sprint with timestamps.  For every item that was completed, it will say burndown.  For items that were introduced into the sprint, it will say scope change. 

[Stefan Salzl]

Hi @Barney Powell ,

I would like to have a look at this with my long years experience as an agile coach as well as a Jira Admin:

• Which information would this kind of report would deliver to you? (you already know the fact that issues are rolled over to other sprints. How would this report help you find a solution?)
• Which insights do you expect from this report?
• Does the team estimate issues (eg. in Story Points)? and if so:
  • Pre-defined reports like burndown chart or velocity would give good inputs on how burndown during sprint works
  • according to that the velocity gives guidance of an averadge what the team is capable of
  • this could show that maybe the team is over-commiting each sprint (obviously)
  • I would suggest to take all these insights to a retrospective with the team and discuss (if not happening in dailies) why eg. stories kept open for several days, if there have been any impediments, if so: which one? where did they come from? Why weren´t they populated at the time of appearance?

I was even looking for something like a JQL that just "does" what you required but I couldn´t come to a solution. However imho sprint reports, burndown charts and velocity are the way to go to improve team operations in sprints.

Best
Stefan