PRs Opened Metric

Definition

PRs Opened measures the total number of pull requests (PRs) created during the selected time range.

It reflects how many new code review workflows were initiated.

This metric includes all PR creation events within the selected repositories and filters.

How the Metric Is Calculated

PRs Opened is calculated as:

Total number of PR creation events within the selected time range

In the dashboard, this value is normalized as: PRs per day

The headline value represents: Total PRs opened ÷ Number of days in the selected time range

This is a normalized daily rate to allow comparison across different time ranges.

How the Metric Is Displayed in the Dashboard

The metric card displays two types of values:

1. Headline Value (e.g., 35.29 PRs per day)

The large number shown at the top represents the average number of PRs opened per day across the selected time range.

This is a daily average — not a total count.

2. Time-Based Values in the Chart

The line chart shows the number of PRs opened per time bucket (for example, per day).

Each point represents: The total number of PRs opened within that specific time bucket

Clicking a point displays:

• The number of PRs opened on that date

Daily bucket values do not average to produce the headline; the headline is calculated independently across the full selected range.

Why This Metric Is Useful

PRs Opened provides visibility into:

• Development workflow initiation
• Team throughput patterns
• Sprint activity levels
• Release cycle intensity

Sustained increases may indicate:

• Active feature development
• Increased collaboration
• Larger team capacity

Unusually low activity may indicate:

• Blockers
• Reduced scope
• Release freeze periods

How to Interpret PRs Opened

PRs Opened measures workflow initiation, not delivery.

It should be interpreted alongside:

• PRs Merged
• Cycle Time
• PR Size
• Review Depth

High PR volume does not necessarily indicate high delivery output.

Context matters — team size, sprint cadence, and release timing all influence this metric.

Data Sources

Derived from:

• Pull Request creation events
• Repository-level filters
• Branch inclusion/exclusion rules

Limitations

• Does not measure code quality.
• Does not measure merge success.
• Large numbers of small or experimental PRs may inflate this metric.
• Does not account for PR size or complexity.

PRs Opened reflects workflow activity, not delivery impact.

Stakeholder Use Cases

Engineering Managers

• Monitor team workflow volume.
• Detect throughput fluctuations.

Team Leads

• Track sprint initiation patterns.
• Identify workflow bottlenecks.

Developers

• Understand contribution volume.

Product Leadership

• Monitor development intensity relative to roadmap phases.