Sprint Scope Still Open(2.4.6)

Every issue that does not finish in its sprint either moves to a later sprint or stays where it was. This visual shows the second case per sprint: how many of a sprint's issues are done now and how many are still open now, so a rising share of unfinished scope can be seen across sprints.

Each issue is counted in the sprint it was most recently assigned to, so an issue moved on to the next sprint counts only there. The split is measured as of now, not at the sprint's close: for a finished sprint the open bar is the scope that was left in it and never moved on, and for the sprint in progress it is simply the work not yet done.

What you can conclude

• An open share above 30 percent on finished sprints means more than three in ten of those sprints' issues are still open and were never moved to a later sprint; a reviewer could ask whether that scope is still wanted.
• A share that grows sprint over sprint means each sprint leaves more of its scope open than the one before; the events show the trend, not its cause.
• A share trending toward zero over multiple sprints means less of each sprint's scope is left open at its end; the trend badge shows the direction at a glance.

How this chart works

Stacked bar chart showing per sprint the number of issues now in a done status (teal) versus those still open (coral). Three KPI badges above the chart show the latest sprint's open share, the trend direction, and the number of sprints analyzed. A dashed line on the secondary axis shows the open share per sprint.

When an issue's sprint field lists several sprints, it counts in the last one listed, and an issue removed from every sprint counts in none. An issue counts as done or open by the latest status its events record. Issues deleted in Jira, issues in a project moved to the trash or deleted and not restored, and issues whose events record no status that maps to a Jira status category are left out of a sprint's bars entirely, and an issue moved to another project counts under its current project.

A coral warning banner is shown when the latest sprint's open share exceeds 30 percent.

Each sprint the chart draws is one bar, identified by its Jira sprint id. A sprint whose name was never recorded, for example one that closed before MetaFrazo started receiving sprint events, is labeled Sprint #<id>, and the caption above the chart counts those bars. When no sprint in the data has a recorded name, an amber banner above the chart says so instead.

Use the project and sprint filters to compare specific sprints or focus on a single team.