Developer | Check-Ins & Merge Requests

Definition (Hover Text)

The Number of Check-In's (commits) & Merge Request's that are merged helps assess transparency and the effectiveness of task breakdown.

Source Tools

Github, Gitlab, Bitbucket, Azure Repo

Graph type

Bar & Line

Filters

Branches & Developers

Hover Format on KPI

Duration: From Date - To Date
No. of Check-ins: XX
No. of Merge Requests: YY

Fields on Explore

• Project

• Repository

• Branch

• Days/Weeks

• Developer

• No. of Commit

• No. of Merge

Business Logic

Calculation Formula

Count of Check-In’s (commits) during a period
Count of Merge Request’s merged during a period

Trend

An increasing value is regarded as a positive trend

Maturity Levels

M1: 0-2

M2: 2-4

M3: 4-8

M4: 8-16

M5: >16

Instance level thresholds

Check-In’s?

27 MR’s

Configurations

Processor Fields

N/A

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 Number of Check-In's reflects both transparency and the effectiveness of task breakdown. A higher number of Check-In's often indicates well-defined, manageable tasks.

The Number of Merge Requests (MR's), when considered alongside commits, provides insight into the efficiency of the review process and how smoothly changes are integrated.