Avg. PR Iteration Time
The average amount of time (in seconds) that pull requests spend in "iteration cycles" - the back-and-forth process between developers and reviewers when changes are requested and implemented.
Where to find it
- Health > Team Insights > Add new metric
- Health > Benchmark > Add new metric
Interpretation
- Low Values (< 2 hours) - indicate very fast iteration cycles and quick responses to feedback, which is positive. However, they may also suggest rushed revisions or insufficient attention to feedback. It’s important to verify the quality and completeness of changes.
- Medium Values (2–8 hours) - reflect a healthy balance between speed and quality, typical for well-functioning teams with effective communication. Consistency should be monitored and opportunities for optimization explored.
- High Values (> 8 hours) - suggest slower iteration cycles, potentially due to communication bottlenecks, complex rework, developer availability, or unclear feedback. These areas should be assessed and addressed as needed.
Custom Dashboards
Don't forget you can anytime include any metric in your Custom Dashboards.
Updated about 24 hours ago