Total Closed Pull Requests

Where to find it

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

Interpretation

• A high number of closed pull requests (without merging) may indicate quality issues, such as poor code standards, inadequate review processes, or weak development practices. It can also point to process inefficiencies, including unclear communication, disorganised review workflows, and lack of team alignment.
• Additionally, high closure rates may stem from incomplete or poorly planned work, skill gaps, or limited team accountability.
• Low closure rates generally reflect strong quality standards and effective development practices. They suggest smooth, efficient review workflows, consistent team communication, and well-aligned coordination.

Custom Dashboards

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