Pull Request Analytics for Bitbucket
📊 Helps teams to improve their software development process and cycle time by making the most out of pull requests
Discoverability: find PR's that need action
Easily find the pull requests that need action with the global list of all open pull requests that can be filtered by project, programming language, due date, size, activity, etc.
Analytics: measure and improve your PR workflow
Visualize key aspects of your PR workflow with statistics on cycle time, lines of code, time to open and distribution workload. Or leverage the retrospective summary to see how teams work with PR's during sprints.
Reminders: get notified for open and due PR's
Get Slack reminders for PR's that need action so they can be reviewed and merged in time. Provides personal as well as repository-wide notifications and also on-demand PR information with Slack commands.
Pull Request Analytics helps teams to improve their pull request workflow and to reduce their cycle time with
- Global pull request list to find pull requests that need action
- Sprint retrospective to improve the pull request workflow for the next sprint
- Visualized key aspects of your pull request workflow with valuable statistics
- Cycle time analysis to see potential issues with long-standing pull requests
- Average lines of code analysis to detect issues with large pull requests
- Time to open statistic to identify time delays on pull requests
- Configurable thresholds for metrics like pull request size or cycle time to define goals for an improved workflow
- Slack reminders for due and open pull requests to review
For more information, please check our documentation.
Want to know more? schedule a live demo with us!
More Bitbucket apps you'll like:
✔️ Improve your pull requests by auto-assigning reviewers and enforce reviews with Code Owners based merge checks - Code Owners for Bitbucket
Privacy and security
PR distribution shows the different PR states at different points in time. You can see if the PR workload was equally spread, or if the merges all happened at the sprint end, possibly having an impact on proper review.