Total Story Points Completed Report
Last updated: October 27, 2026
Total Story Points Completed (shown in Span as Total Estimate Completed) is the sum of story points on every issue completed in the date range. It weights delivery by your team's own estimates instead of counting issues.
Why it matters
Issue counts treat a one-line fix and a large feature the same. Summing estimates gives a more useful view of delivered volume when your backlog mixes issues of very different sizes. Use it to set a velocity baseline for sprint planning, forecast delivery for roadmap work, see how unplanned work affects completion, and understand how points are spread across team members.
How it works
Total Story Points Completed = SUM(story points) on issues whose current status is DoneSpan uses each issue's latest estimate. For Jira, it reads the story point field set on the integration, or the field it detected as story points. For Linear, it reads the issue estimate.
Done means the issue's status maps to Done in your tracker's status categories. Each issue lands on its completion date.
Issues without an estimate add 0.
Span credits each issue to its most recent assignee who maps to a person in Span.
Related variants:
Metric | What it measures |
|---|---|
Story Points Completed Per Week (Estimate Completed / Week) |
|
Planned Completed (points) | In Sprint Tracking: points on planned issues done by sprint end |
Unplanned Completed (points) | Points on issues added a day or more after sprint start and done |
In Progress / In Review (points) | Points on issues in an In Progress category status, or a status named "In Review", at sprint end |
Rolled Over (points) | Points on unfinished issues still in the sprint when it ended |
Estimate Planning Accuracy | Planned points completed ÷ planned points |
Sprint metrics use each issue's estimate as of sprint end, not its latest estimate.
Setup
Connect Jira or Linear, with story points set on your issues.
For the per-week variant, connect a calendar or HRIS for out-of-office days.
Set up teams and contributors in Span.
Find the metric in Insights → Productivity → Velocity → Issue lifecycle, on team and person pages, and in custom reports and dashboards. Search for "Total Estimate Completed". Break it down by person, team, team hierarchy, job family, and issue type, over any date range or by week, month, or quarter. Sprint-level point metrics are in Insights → Productivity → Sprint Tracking.
Things to know
Worked example: a team completes 120 story points over a 2-week period with 60 active person-days. Total Story Points Completed is 120. Story Points Completed Per Week is (120 ÷ 60) × 7 = 14 points per person per week.
Scales aren't normalized: if Team A uses a 1 to 13 Fibonacci scale and Team B a 1 to 8 linear scale, Span sums both directly. Teams with larger scales look more productive, and raw totals aren't comparable across teams that estimate differently. Compare each team's trend instead, and analyze teams separately when scales differ.
Latest estimate: re-estimating an issue after completion changes history for this metric.
Sub-tasks and epics count: points on both a story and its sub-tasks both count. Jira's velocity chart ignores sub-task estimates.
Totals depend on period length and time off: use the per-week variant to compare periods or teams fairly.
Assigned issues only: report views count issues assigned to someone Span can match to a person.
Inconsistent estimates: if your team doesn't estimate consistently, use Issues Completed instead.
Good practice. Set a baseline from 3 to 6 sprints of history, set aside sprints with major disruptions, and refine the baseline as the team changes. Read points next to issue cycle time (how long active work takes) and quality metrics, and use retrospectives to explain the numbers.
Related articles
Story Points Completed Per Week Report
Need help?
Contact your Span account team or reach out to support@span.app.