Pull Request Activity shows how many pull requests were created, merged, or are currently open during the selected period. It's the simplest signal for "are we shipping work?" and a useful counterweight to Lead Time and Deployment Frequency.
What it measures
PRs created in the period.
PRs merged in the period.
PRs currently open as of the end of the period.
How Leanmote calculates it
prs_created = count(prs where opened_at in period) prs_merged = count(prs where merged_at in period) prs_open = count(prs where merged_at is null and closed_at is null at period_end)
Bot-authored PRs are excluded when bot accounts are tagged in your team mapping.
Drafts are typically excluded from "created" until promoted to ready-for-review (configurable).
How to interpret it
Created > merged consistently — the team is opening more than it's finishing. Watch for review queue growth.
High open count with stable created/merged — work is piling up. Pair with WIP and Avg Age of WIP.
Created and merged track each other — healthy pull-based flow.
What to do about it
If open PRs are growing, run a stale-PR sweep weekly. Close abandoned ones, push the slow ones.
If created is dropping but merged isn't, you may have a planning gap — fewer items started this week.
Use this metric alongside Throughput (issue-level) to confirm code-side and planning-side flow agree.
Related metrics
Lead Time for Changes
Deployment Frequency
Throughput
Avg Member Time to Merge