Tracking PR Link Rate in Targets

Last updated: October 27, 2026

PR Link Rate is the percentage of merged pull requests (PRs) linked to at least one issue in your issue tracker. Use it to keep code changes traceable to planned work and to track linking discipline as a team norm in Targets.

Why it matters

When PRs aren't linked to issues, you lose the thread between code and the work it was meant to do:

  • For reviewers: a linked issue gives the "why" behind a change, with requirements, acceptance criteria, and discussion one click away.

  • For product and planning: issue status reflects code that actually merged, so roadmap tracking and issue metrics such as Issue Cycle Time and Issues Completed / Week stay reliable.

  • For compliance: a high link rate is evidence that changes trace back to tracked requirements (for example for SOC 2 or ISO 27001 audits).

  • For engineering leaders: unlinked PRs reveal hotfixes, tech debt, and other work that bypasses planning.

How it works

PR Link Rate = merged PRs with at least one linked issue ÷ Total PRs merged × 100

  • Only merged PRs count. Reverted PRs leave the calculation.

  • Only PRs by people marked Contributor count. Accounts Span can't map to a person, such as most bots, drop out.

  • A PR needs one linked issue to count as linked. More links don't change the count.

  • Span reads the PR links your issue tracker records (Jira, Linear, GitHub Issues, or Azure Boards). Whether a branch name, commit message, or "Closes #123" in a PR description creates a link depends on your tracker.

  • Links added after a PR merges still count, in the period the PR merged.

Where to find it: Insights > Productivity > Velocity > Issue lifecycle, alongside Issue Completion Rate, Issues Completed / Week, and Issue Cycle Time. Break it down by person, team, or repository, and compare against percentile benchmarks. Click the chart to see the unlinked merged PRs for a period.

Low PR Link Rate signal: Span compares a team's link rate over the most recent 2 weeks with its rate over the 8 weeks before that. When the recent rate is 30 percentage points or more lower, Span shows a Low PR Link Rate signal in Span and in the daily brief.

Setting up PR Link Rate in Targets

  1. Connect a version control integration (GitHub, GitHub Enterprise Server, GitLab, or Azure DevOps; Bitbucket Cloud is available and Span turns it on for your organization on request) and an issue tracker (Jira, Linear, GitHub Issues, or Azure Boards).

  2. Go to Targets in Span.

  3. Add the PR Link Rate target for your team.

  4. Set your target threshold, for example 85%.

  5. Review the team's progress in team meetings. When the rate falls sharply, the Low PR Link Rate signal appears on the team overview and in the daily brief. PR Link Rate doesn't send per-PR alerts.

Suggested targets based on where you start: below 50%, aim for 70% within 3 months; 50–70%, aim for 85%; 70–85%, aim for 90% or more; above 85%, hold the level and look into any drop.

Things to know

  • The signal threshold is in percentage points. Worked example: a team's 8-week baseline is 80%. If the last 2 weeks come in at 55%, the drop is 25 points and no signal appears. If they come in at 48%, the drop is 32 points and the signal appears.

  • 100% is rarely the right goal. Docs-only changes, dependency updates, typo fixes, and emergency hotfixes are reasonable exceptions. Many teams target 90–95% and create issues for hotfixes after the fact.

  • A link isn't proof the link is right. A 95% rate can still hide PRs linked to catch-all "miscellaneous" issues. Spot-check a sample of linked PRs.

  • Very high rates with low throughput can mean engineers create issues only to satisfy the metric. Watch for busywork.

  • History can change. Because Span counts links added after merge, linking old PRs raises past periods.

  • Check integrations first when the rate looks wrong. Issues in projects Span doesn't sync can't link, so their PRs read as unlinked.

Practices that help: put issue keys in branch names (for example feature/ABC-123-auth-refactor), add an issue link section to your PR template, add a CI check that fails when a PR has no linked issue, ask reviewers to confirm the link before approving, and include linking in onboarding.

Related articles

PR Link Rate Report (calculation details)

Issue Completion Rate Report

Issues Completed / Week

Total PRs Merged

Need help?

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