How to Create a Sprint Rollover Report

[Ian Lundy]

Hi!

I want to create a report that captures stories that rollover from sprint to sprint. I want to create a report that shows the following:

• The original sprint the story was planned in (I think this is the Sprint Commitment?)
• The sprints it rolled over into even if that sprint is in the future (i.e., from Sprint 2 to Sprint 3 to Sprint 6)
• The current sprint. 

I've created a filter that shows the Sprint Commitment and the Sprint. The problem is that sometimes the Sprint Commitment changes. See MSLDSH-4330 in the screenshot. The Sprint Commitment for that story should be Sprint 17, but it shows as Sprint 18. The screenshot shows all stories in the current sprint. 

Also, when I use the filter to look at the previous sprint, it doesn't show all the stories committed to that sprint. Somehow the Sprint Commitment changes for some stories in this scenario also.

How do I create a report that shows this information?

Thanks in advance!

[Trudy Claspill]

Hello @Ian Lundy 

Welcome to the Atlassian community.

The Sprint Commitment field is not natively provided by Jira. That field must have been added either by a Jira Administrator or by the addition of a third party app. Without knowing the configuration of the field and its source, we can't speculate on the data it should or should not return.

[Ian Lundy]

Hi Trudy,

This answer makes me so sad. You've crushed all my hopes and dreams. (I'm kidding :)) Thanks for the quick response!

Warmly,

Ian

[Trudy Claspill]

Sorry :-(

I recommend that you check with your Jira Administrators to find out the source of the field, and to get more information would how it should be working. If it is from a third party app, if you provide that information here a community member might be able to provide more information about the app.

[Zane eazyBI Support]

Hi @Ian Lundy ,

If you are comfortable using a third-party app, you can analyse Sprint scope and changes with eazyBI (https://marketplace.atlassian.com/apps/1211051/eazybi-reports-and-charts-for-jira).

eazyBI maintains the complete history and can show which sprints an issue has been part of, even if it moves across multiple sprints. It gathers facts from the issue change history and, based on that, provides metrics to see which issues were committed to the sprint and which were added later after the sprint started, which issues were removed from the sprint and which remained until the end, and in what statuses they were at the end of the sprint. For issues that move across multiple sprints, eazyBI maintains accurate historical data about when issues were originally committed vs. added later.

You can measure sprint scope using either story points, issue count, or even estimated and logged hours.

Here's a popular demo report that shows the sprint's initial scope (commitment) and changes during the sprint (added and removed work items). Users can interact with the report to see the exact work items behind the numbers: https://eazybi.com/accounts/1000/cubes/Issues/reports/80617-sprint-issues-by-status-category-at-sprint-end.

You can also explore our Sprint overview dashboard with multiple sprint scope reports:
https://eazybi.com/accounts/1000/dashboards/5956-sprints-overview.
This is a public Demo account and does not require any login.

Best,

Zane / support@eazyBI.com

[Alexey Pavlenko _App Developer_]

Hi @Ian Lundy ,

Unfortunately, it's impossible to achieve with native JIRA - you won't get consistent reports. You can use the app I developed for this - Multi-team Metrics & Retrospective. With it, you will be able to get this view:

• The original sprint the story was planned in (I think this is the Sprint Commitment?) = Initial Scope/Final Scope
• The sprints it rolled over into even if that sprint is in the future (i.e., from Sprint 2 to Sprint 3 to Sprint 6) = Removed Scope
• The current sprint = SI Sprint 61 or Network Sprint 46

Plus, conduct in-place and quantifiable retrospectives - feel free to read this detailed article.

Best regards,
Alexey