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.
Who can use this?
Which reports use Reaction time?
What does Reaction time measure?
Reaction time helps you understand how long it takes for PRs to get reviews.
Use Reaction time alongside Responsiveness to pinpoint what part of the review process is causing PRs to be open and unread for longer than necessary. A high Reaction time could mean reviewers are not responding to submitted PRs quickly or not responding at all.
How is Reaction time calculated?
Reaction time is calculated as the sum of all reviewer response times divided by the number of reviewer responses.
Reviewer response time is the time between a submitter action and a reviewer response.
A reviewer is any user who comments, commits, reviews, approves, merges, or closes a submitted PR. Reaction time calculates the reviewer response time between a submitter action and each user’s first comment on the action.
A reviewer response is the first reviewer comment, commit, review, approval, merge, or closure immediately preceded by a submitter action. A submitter action is a commit, comment, merge, or closure from the PR’s submitter.
Note: Flow Enterprise Server only calculates Reaction time for the first reviewer’s first reaction following a submitter action. It doesn't calculate Reaction time for subsequent reviewers.
What data is included in Reaction time?
Reaction time treats reviewer actions from a single reviewer without submitter actions between them as a single submitter action. It only counts the first submitter action from that submitter when finding response time.
If there are multiple reviewer actions in a row from different reviewers, Reaction time counts the first reviewer action from each reviewer.
Reviewer actions aren't included in Reaction time if:
- The reviewer is excluded from reports.
- The reviewer is a hidden user.
- The comment or commit is excluded.
PRs aren't included in Reaction time if:
- The PR is unmerged.
- The PR is created by a user who is excluded from reports.
- The PR is created by a hidden user.
- The PR is an excluded pull request.
- The PR is from a deleted repository.
- The PR is deleted from a repository.
- The PR doesn’t get a reviewer action.
If you need help, please contact Pluralsight Support.