Developer | Revert Rate

Definition (Hover Text)

Revert Rate is the percentage of pull requests reverted after merging due to issues like bugs or conflicts, reflecting code stability and review effectiveness.

Source Tools

Github, Gitlab, Bitbucket, Azure Repo

Graph type

Line

X Axis - Days/Weeks/Months
Y Axis - Percentage

Filters

Branches & Developers

Hover Format on KPI

<From Date - To Date>: <Revert Rate %>

Fields on Explore

• Project

• Repository

• Branch

• Developer

• Days/Weeks

• No. of Merges

• Revert PRs

• Revert Rate

Business Logic

Calculation Formula

Revert Rate is calculated by dividing the number of reverted pull requests by the total number of pull requests raised within a specific time period, then multiplying by 100 to express it as a percentage.

Revert Rate (%) = (Number of reverted PRs / Total number of PRs) × 100

Trend

A decreasing revert rate is a positive trend.

Maturity Levels

M1: > 80%
M2: 50 - 80%
M3: 20 - 50%
M4: 5-20%  
M5: <5%

Instance level thresholds

50

Configurations

Processor Fields

Nil

KPI Specific fields

Target KPI Value

How to Validate KPI

Suggested ways of working

• Ensure accurate tracking of pull requests that have been reverted, including timestamps for the original merge and the subsequent revert.

• Clearly label or tag reverted pull requests to differentiate them from other changes.

• Standardize the workflow for identifying and logging reverted changes to ensure consistency across teams.

Sample JQLs

N/A

Benefits of KPI

How does the KPI help

The Revert Rate KPI helps by highlighting issues with code quality and the effectiveness of the review and testing processes. A high revert rate signals potential problems, such as insufficient testing or poor code review, which can lead to wasted effort and instability. By tracking this KPI, teams can focus on improving code stability, reducing rework, and enhancing the overall development process.