The PR resolution report reviews merged PRs for key health indicators to support healthy work patterns.
Use PR resolution to filter for outliers in a team's work patterns. Use the distribution charts to identify the root cause of outliers in productivity. Additionally, view trends for time elapsed to merge and first comment for PRs.
Who can use this?
With PR resolution, team leads, managers, and executives can:
- Understand a team's PR activity trends and use these patterns to support work trends.
- Identify normal patterns and outliers in the code review process.
- Track progress against collaboration targets.
- Review merged PRs to spot teams’ trends.
To find the PR resolution report:
- Click Reports in Flow's top navigation bar.
- Click PR resolution located in the left navigation under Team processes.
Time to merge
Pull requests: time to merge shows all pull requests merged during a selected period.
Use Time to merge to:
- View patterns in your team's PR resolution practices.
- Manage your team’s productivity trends.
- Compare your team’s productivity against targets.
The x-axis shows when a PR it was merged. The y-axis shows how long it took to merge the PR.
Note: If the Weighted toggle is On, the y-axis on the Time to merge graph shows Time to merge divided by Impact. For each merged PR, Time to merge is divided by the Impact for the PR. If the Weighted toggle is Off, the y-axis shows only Time to merge.
Use the Time to merge graph to filter for outliers. This helps you see if your team is meeting their targets.
For example, if your team’s Time to merge is higher than your target, you want to see those trends going down. Review this chart weekly or biweekly to ensure those trends are improving.
If your Time to merge is close to your target, use this report to look into other times where Time to merge is high. This helps you identify issues that cause outliers.
This section shows key metrics on PRs merged during a selected period. These graphs help you identify outliers and manage the root causes of productivity variation.
Note: Closed PRs are not counted toward the metrics calculations in this report.
Use these graphs to gauge how your team is performing. You’ll see the median values for PR metrics. You'll also see maximums, minimums, and targets where applicable.
Tip: If you’d rather see the average Time to merge and Time to first comment metrics, use Team health insights.
Click a column to view the details of those PR metrics in the PR list below. For example, if your maximum is 75 hours, you might want to look into the PRs that took longer and see where your team can improve.
To view PR details, click the column you want more information about. View the specific PRs and participant details in the PR timeline at the bottom of the page. Hover over any listed PR for an overview of that PR.
Note: Flow determines PR size by the PR’s total lines of code. Small PRs have fewer than 13 lines of code. Medium PRs have fewer than 151 lines of code. Large PRs have more than 151 lines of code.
To keep the PR overview open on the page, click the PR and select Pin PR details from the resulting dropdown menu. To open the PR in a new tab, click the PR and select Open PR from the resulting dropdown menu.
Click the Participants tab for a list of engineers who contributed to the PR with an overview of their contributions.
If you need help, please email Support (opens email form) for 24/7 assistance.