Permissions
Org Admin | Team Manager (for assigned team) | Org Contributor | External Contributor |
View | View | View | No access |
The Pull Requests page in devActivity provides a comprehensive overview of all pull requests (PRs) within your selected repositories. This page enables you to:
Identify bottlenecks: Analyze PR processing times to pinpoint stages that are slowing down development.
Improve efficiency: Optimize workflows and reduce cycle times based on data-driven insights.
Track team performance: Monitor team progress and identify areas for improvement.
Make informed decisions: Use real data to make informed decisions about resource allocation and process changes.
Filtering and Sorting
The Pull Requests page offers powerful filtering and sorting options to tailor your analysis:
Repository: Select specific repositories to focus your analysis.
Status: Filter by PR status (e.g., open, merged, closed).
Contributor: Focus on PRs from specific developers.
Period: Define a timeframe for analysis (e.g., last week, past month).
You can sort the data by any of the columns, including:
Cycle Time: Total time from PR creation to merging.
Coding: Time spent actively writing code.
Pickup: Time taken for a reviewer to start reviewing.
Review: Time spent on code review.
Pull Request Details
Each row in the Pull Requests table represents a single PR and includes:
Author: The PR creator.
Pull Request: The PR title, providing context.
Work Quality Metrics
The Pull Requests page displays key metrics to assess PR processing efficiency:
Cycle Time: Total time from PR creation to merging.
Coding: Time spent actively writing code.
Pickup: Time taken for a reviewer to start reviewing.
Review: Time spent on code review.
These metrics help you identify bottlenecks in specific stages of the PR process. For example, a long Pickup Time may indicate that reviewers are overloaded or that the PR is not communicated.
Benefits and Applications
The Pull Requests page provides valuable insights to help you:
Identify bottlenecks: Pinpoint stages in the PR process that are slowing down development.
Improve efficiency: Optimize workflows and reduce cycle times.
Track team performance: Monitor team progress and identify areas for improvement.
Facilitate data-driven decisions: Make informed decisions about resource allocation and process changes based on real data.
By using the Pull Requests page effectively, you can streamline your development process, improve team collaboration, and deliver high-quality code faster.
Recommendations
Filter by period and sort by specific metric to identify operational bottlenecks.
Share an idea of what kind of data/metric related to Pull Request might be useful.
Questions, Ideas, Improvements