Developer | PR Success Rate
Overview | |
---|---|
Definition (Hover Text) | Pull Request (PR) Success Rate measures the percentage of pull requests that are successfully merged without being abandoned or discarded, compared to the total number of PRs raised within a given period. |
Source Tools | Github, Gitlab, Bitbucket, Azure Repo |
Graph type | Line X Axis - Days/Weeks/Months |
Filters | Branches & Developers |
Hover Format on KPI | <From Date - To Date>: <PR Success Rate %> |
Fields on Explore |
|
Business Logic | |
Calculation Formula | PR Success Rate is calculated by dividing the number of successfully merged pull requests by the total number of pull requests raised during a specific period. The result is expressed as a percentage.
|
Trend | An increasing PR Success Rate is a positive trend. |
Maturity Levels | M1: < 5% |
Instance level thresholds | 50 |
Configurations | |
Processor Fields | Nil |
KPI Specific fields | Target KPI Value |
How to Validate KPI | |
Suggested ways of working |
|
Sample JQLs | N/A |
Benefits of KPI | |
How does the KPI help | The PR Success Rate helps by providing insight into the efficiency of the development process. A high success rate indicates that most pull requests are being successfully merged, suggesting smooth collaboration, good code quality, and effective review processes. A low or declining success rate may signal inefficiencies, such as unclear requirements, code quality issues, or bottlenecks in the review process, helping teams identify areas for improvement and reduce wasted effort. |
© 2022 Publicis Sapient. All rights reserved.