Pull request and collaboration metrics

Review metrics provide software teams insight into what’s happening in the code review process. Review metrics include: Reaction time is the average number of hours it takes for a reviewer to respond to a set of PRs as a reviewer. Invo...

The submitter metrics make it easy to understand how PR submitters are responding to and incorporating feedback from the code review process. In this article Submit Metrics Responsiveness Unreviewed PRs Comments Addressed Receptive...

The Team collaboration metrics are designed to give managers a bird's-eye view of how their teams are behaving in the code review process. These metrics illuminate knowledge concentration centers, code that may require your attention, and bottl...

Time to merge is the average time in hours from when pull requests are created to when they are merged, rounded to the nearest tenth of an hour.   Note: If your Pull request tracking is set to First commented , the pull request cre...

Time to first comment is the average time in hours from when pull requests are created to when they receive their first comment, rounded to the nearest tenth of an hour.   Note: If your Pull request tracking is set to First commen...

Unreviewed PRs is the percentage of merged pull requests that have no comments or approvals from non-submitter reviewers, rounded to the nearest tenth of a percent. In this article Which reports use Unreviewed PRs? What does Unreviewed PRs...

Responsiveness is the average number of hours it takes for a submitter to respond after a reviewer action, rounded to the nearest tenth of an hour. In this article Which reports use Responsiveness? What does Responsiveness measure? How i...

Reaction time is the average number of hours it takes for an individual or team to respond to a set of PRs as a reviewer. In this article Which reports use Reaction time? What does Reaction time measure? How is Reaction time calculated? ...