Overview | |
|---|---|
Definition (Hover Text) | Mean time to merge measures the efficiency of the code review process in a a team |
Source Tools | Github, Gitlab, Bitbucket, Azure Repo |
Graph type | Line |
Filters | Branches |
Hover Format on KPI | Mean time to Merge <Hours> |
Fields on Overlay | |
Business Logic | |
Calculation Formula | Difference of time between when PR was raised and the time when PR was merged. The average of all merged PRs in a week is 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 | N/A |
Configurations | |
Processor Fields | |
KPI Specific fields | Target KPI Value |
How to Validate KPI | |
Suggested ways of working | |
Sample JQLs | |
Benefits of KPI | |
How does the KPI help | |
General
Content
Integrations