Avg. to issue PR

Where to find it

• Health > Benchmark > Add new metric
• Health > Team Insights > Add new metric

Interpretation

Larger Companies

• High: Less than 48 hours. – indicate teams can open PRs quickly despite enterprise scale. This usually reflects small, well-scoped tickets, short-lived branches or trunk-based practices, strong CI automation, and clear requirements. Watchouts: fragmented PRs, rushed changes, or insufficient coordination with dependent teams.

• Medium: Between 48 and 72 hours. – a healthy pace for most enterprises. It allows time for integration tests, cross-team reviews, security/lint checks, and QA or design sign-offs while keeping flow steady. Typically signals good work item sizing, reliable CI/CD, clear ownership, and predictable planning.

• Low: More than 72 hours. - may point to bottlenecks such as oversized work items, unclear acceptance criteria, heavy approval chains, slow/flaky CI, environment constraints, cross-team dependencies, or release-train coupling. Consider splitting work, using draft PRs earlier, reducing required reviewers where appropriate, parallelising testing, and speeding up CI.

Smaller Companies

• High: Less than 2 hours - suggest developers are quick to share their work, likely due to confidence in code quality, a smooth workflow, and well-understood requirements. However, this speed could also reflect rushed work or inadequate testing.
• Medium: Between 2 and 8 hours - reflect a balanced pace that allows for proper implementation and testing. This is typical for effective teams and indicates solid development practices and a healthy trade-off between speed and quality.
• Low: More than 8 hours - may signal inefficiencies in development. Contributing factors could include complex tasks, unclear requirements, over-polishing, lack of proper tools, or low confidence in the code.

Custom Dashboards

Don't forget you can anytime include any metric in your Custom Dashboards.