Total Open Pull Requests

Where to find it

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

Interpretation

• A high number of open pull requests may indicate review bottlenecks caused by slow approval cycles, insufficient reviewer capacity, or inefficiencies in the review process. It can also reflect workflow issues such as poor team coordination, inadequate review coverage, or weak process discipline.
• Additionally, it may point to capacity constraints, including team overload, resource shortages, or poor workload distribution. In some cases, it may signal quality concerns due to rushed development and limited time for thorough reviews.
• A low number of open pull requests generally reflects an efficient and well-managed development workflow. It suggests fast and effective review cycles, strong team coordination, and disciplined adherence to established processes. This typically indicates adequate reviewer capacity, balanced workload distribution, and high overall team performance.

Custom Dashboards

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