PRs Created counts the total pull requests a single team member opened during the selected period. It's a contribution-volume signal — useful for understanding individual activity and as input to capacity planning.
What it measures
The number of pull requests where this member is the author and opened_at falls within the period.
How Leanmote calculates it
prs_created = count(prs where author = member and opened_at in period)
Counts both merged and unmerged PRs as long as they were opened in the period.
Drafts are typically excluded until promoted to ready-for-review (configurable).
Bot accounts mapped in your team setup are excluded.
How to interpret it
Compare to the team's median, not to other members directly. Different roles produce different PR cadences.
High PR count with low merge rate can indicate work-in-progress accumulation or PRs being abandoned.
Sharp drops often reflect PTO, on-call rotations, or context shifts (e.g., heavy review week instead of authoring).
What to do about it
Don't use this as a productivity ranking. Mix of role, item type, and PR size all distort it.
Use alongside Avg Member Time to Merge and Reviews Count to get a fuller picture of contribution.
Related metrics
Pull Request Activity
Reviews Count (per member)
Commits Count (per member)
Avg Member Time to Merge