Developer | Mean Time To Merge

Definition (Hover Text)

Mean Time to Merge measures the efficiency of a team's code review process.

Source Tools

Github, Gitlab, Bitbucket, Azure Repo

Graph type

Line

X Axis - Days/Weeks/Months
Y Axis - Count (Hours)

Filters

Branches & Developers

Hover Format on KPI

<From Date - To Date>: Hours

Fields on Explore

• Project

• Repository

• Branch

• Days/Weeks

• Developer

• Merge Request URL

• Mean Time to Merge (In Hours)

Business Logic

Calculation Formula

Mean Time to Merge is calculated as the difference between the time a Pull Request (PR) was raised and the time it was merged.
The average time of all merged PRs within a duration is then plotted on the graph.

Trend

A decreasing trend is considered positive.

Maturity Levels

M1: > 48 Hours
M2: 16 - 48 Hours
M3: 8 - 16 Hours
M4: 4-8 Hours 
M5: < 4 Hours

Instance level thresholds

55

Configurations

Processor Fields

Nil

KPI Specific fields

Target KPI Value

How to Validate KPI

Suggested ways of working

• Encourage timely code reviews to reduce delays.

• Break down tasks into smaller, manageable pull requests.

• Foster clear communication between developers and reviewers.

• Set expectations for review timelines and follow up if needed.

• Automate testing to reduce bottlenecks and expedite the merging process.

Sample JQLs

N/A

Benefits of KPI

How does the KPI help

The Mean Time to Merge KPI measures how efficiently pull requests are reviewed and merged. It helps identify delays or bottlenecks in the review process, improving overall team productivity.