Total Time: PRs Iterations
The total amount of time (in seconds) that all pull requests spent in "iteration cycles" - the back-and-forth process between developers and reviewers when changes are requested, made, and re-reviewed.
Interpretation
- Low Values (e.g., < 12 hours / PR) - efficient review process with minimal back-and-forth. Indicates well-prepared initial submissions, clear review feedback, good communication between developers and reviewers, simple, straightforward changes.
- Medium Values (e.g., 12-48 hours / PR) - normal iteration time for most teams. Indicates: reasonable level of collaboration and refinement, balanced review process, moderate complexity in changes, healthy discussion and improvement cycles.
- High Values (e.g., > 48 hours / PR) - excessive iteration time may indicate process inefficiencies. Potential Issues: poor initial code quality requiring extensive rework, unclear or conflicting review feedback, communication breakdowns between developers and reviewers, overly complex changes that should be broken down, inexperienced developers or reviewers.
Custom Dashboards
Don't forget you can anytime include any metric in your Custom Dashboards.
Updated about 24 hours ago