🎯Pull Request
Pull Requests are the holy grail of any software development process, and getting a 360-degree view into them, and the ability to filter to see the PRs that may require your attention is necessary.
You can use data on this screen to:
Consistently get a view of the process, proactively coach the team and remind them of your best practices or SLA.
Show the reviewer reviewing most PRs and schedule a knowledge-sharing session.
Look at the PRs that are open for longer, and clear roadblocks to push them to production.
If your average cycle time is higher than expected, you can look at the PRs or engineers swinging the most toward this number.
Graphical view
The graphical view shows five trend charts that help you spot patterns over time.
PR Overview
Shows the number of PRs opened and PRs merged per time interval. Use this to track throughput trends and see whether your team is keeping up with review demand or building up a backlog.
PR Size vs Review Time
Compares PR size categories (small, medium, large, extra-large) against the average review time for each size band. Use this to understand whether larger PRs are slowing down your review process.
Cycle Time Analysis
Shows how many PRs exceeded the cycle time threshold (default: 5 days) in each time interval.
Unaccounted PRs
Shows merged PRs with no linked Jira or ClickUp ticket over time - a signal for work that isn't being tracked in your project management tool.
Top Modified Repos
Shows the most active repositories by PR count, with each bar broken down into New Work, Rework, and Maintenance categories. Use this to spot repos with unusually high maintenance or rework ratios.
Tabular View
Major metrics and what they mean
Release Merge Frequency is the total number of PRs merged to release branch in that selected time period/total number of days in the selected time period.
Hotfix Rate is the number of hotfix PRs merged to release branch over the total number of PRs merged to release branch.
Hotfix Resolution Rate shows the average cycle time of the hotfix PRs.
Unreviewed PRs gives the number of PRs that were merged without any approval.
Other metrics and filters:
Unaccounted Work includes all PRs that are not linked to Jira or any other project management tool's tickets.
Ready to Review shows all PRs that are open and are pending a review or approval.
Ready to Merge shows all PRs that have been approved and are awaiting merge.
PRs > 400 LoC helps you track larger PRs over a certain number of lines of code in the selected time period. The larger the PR, the slower it moves through the review cycle and the higher the probability of bugs.
The threshold of 400 LoC is modifiable from Configurations screen.
Cycle time > 5 days shows all PRs merged in that time period with cycle time greater than 5 days.
The threshold of 5 days is modifiable from Configurations screen.
Flashy Review is used to identify PRs which were reviewed very fast and indicate ineffective review. By default PRs > 200 LoC with a review time < 5minutes, are considered flashy, but this is configurable.
By default, the PRs are filtered are based on the author of the PR which is filtered on the Teams and User filter - but this can be adjusted in the PR screen by selecting "Reviewed By" or "Closed By".
Last updated