Page Comparison

Definition (Hover Text)

Mean time Time to merge Merge measures the efficiency of the a team's code review process in a a team

Source Tools

Github, Gitlab, Bitbucket, Azure Repo

Graph type

Line

Y Axis - Hours

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

Filters

Branches & Developers

Hover Format on KPIMean time to Merge <Hours>

<From Date - To Date>: Hours

Fields on OverlayExplore

• Project

• Repository

• Branch

• Days/

• Weeks

• Developer

• Merge Request URL

• Mean Time to Merge (In Hours)

Business Logic

Calculation Formula

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

Trend

A decreasing trend is considered Positivepositive

Maturity Levels

M1 : > 48 Hours

M2 : 16 - 48 Hours

M3 : 8 - 16 Hours

M4 : 4-8 Hours, 

M5 : <4 Hours

Instance level thresholds

N/ANil

Configurations

Processor Fields

Nil

KPI Specific fields

Target KPI Value

How to Validate KPI

Suggested ways of working

TBD

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.