Issues Completed / Week

Last updated: October 27, 2026

Issues completed / week shows how many issues one person finishes in a typical week. It's a per-person rate that adjusts for time off, so you can compare teams of different sizes and periods with different holidays.

Why it matters

Delivery trends: see whether a team completes more or fewer issues over time.
Capacity planning: historical rates help you size sprint and quarterly commitments.
Speed versus slicing: pair it with Issue Cycle Time to tell whether a change comes from faster work or from how the team splits work into issues.

How it works

Issues completed / week = issues completed ÷ non-OOO person-days × 7

Numerator: issues whose current status maps to Done and whose completion date falls in the range. An issue with no completion date lands on its creation date.
Owner: Span credits each issue to one person, chosen from everyone ever assigned to it who maps to a person in Span: the most recently assigned person marked Contributor, or, if none of them is a Contributor, the most recently assigned of the rest. A team's count includes issues assigned to its members.
Denominator: every calendar day in the range for the same people, minus their out-of-office (OOO) days. Weekends count. With a calendar source, a weekday is OOO only when out-of-office events cover more than 4 hours between 8am and 6pm; a shorter block leaves a full day. With an HRIS source, every weekday inside an absence is OOO.
Span divides the totals and multiplies by 7. A team value is the team's total issues ÷ the team's total days × 7, not an average of each person's rate. If the denominator is 0, Span shows 0.

Where to find it: Insights > Productivity > Velocity > Issue lifecycle. It also appears in custom reports, custom dashboards, and team and person pages, with percentile ranks. Break it down by person, team, job level, job title, job family, location, or tenure.

By issue type: Story, Task, Bug, Sub-task, and Epic variants count only that type. They need Jira and match the Jira issue type name; custom types don't match any of them.

Setup

Connect your issue tracker (Jira, Linear, GitHub Issues, or Azure Boards).
Check that your tracker's done statuses map to Done. For Jira, this follows the status category.
Connect an OOO source (calendar or HRIS) so time off leaves the denominator.
Make sure assignees in your tracker map to people in Span.

Things to know

Worked example. Five engineers over 14 days have 70 person-days. One takes 4 OOO days, so the team has 66 days. They complete 40 issues. Issues completed / week = 40 ÷ 66 × 7 = 4.2. If those 4 days had been 4-hour afternoon blocks instead, none would be OOO: 40 ÷ 70 × 7 = 4.0.
The denominator includes everyone in scope. Unlike PR metrics, this rate doesn't filter to people marked Contributor or to people with recent code activity. Managers and other non-coders in the team you're viewing add days and lower the rate.
Weekends count in the denominator, which is why Span multiplies by 7. The weekend exclusion setting doesn't change this metric.
OOO completions still count. Issues completed on someone's OOO day stay in the numerator; only the denominator drops OOO days.
Every issue type counts in the main metric. A story with three sub-tasks counts as four. Use the per-type variants to compare like with like.
Canceled work can count when your tracker maps a canceled status to Done.
Reopened issues that are open today don't count; when they close again they land on the new completion date.
Unassigned issues, and issues assigned to someone Span can't match to a person, don't show in report views.
Why it differs from your tracker: trackers usually show raw totals. Span shows a per-person weekly rate.

Issue Throughput Report

Estimate Completed / Week Report

How to read Span's "/ week" metrics

Issue Completion Rate Report

OOO Person-Days

Need help?

Contact your Span account team or reach out to support@span.app.