Total Failed Pull Requests

Tracks the total number of pull requests that failed during the specified time period.

Where to find it

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

Interpretation

  • Failed pull requests delay feature delivery and bug fixes, developers spend more time spent debugging, reworking, and resubmitting failed PRs. Failed PRs often indicate code quality issues that could lead to production bugs, security vulnerabilities, performance problems & maintenance difficulties.
  • High failure rates can demotivate developers by creating frustration and burnout, reduce code review participation and increase time spent on rework vs. new features. Failed PRs consume developer time for fixes, reviewer time for re-reviews, CI/CD pipeline resources and infrastructure costs for repeated builds.
  • Failed PRs serve as early warning indicators for systemic code quality issues, team skill gaps, process inefficiencies or technical debt accumulation.

Custom Dashboards

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