Developer | Check-Ins & Merge Requests

Definition (Hover Text)

The number of Check-Ins (commits) and Merged Pull Requests (Merge Requests) helps evaluate transparency and the efficiency of task breakdown.

Source Tools

Github, Gitlab, Bitbucket, Azure Repo

Graph type

Bar & Line

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

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 Check-ins

• No. of Merge Requests

Business Logic

Calculation Formula

Count of Check-Ins (commits) during a period.
Count of Merged Pull Requests (Merge Requests) 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

55

Configurations

Processor Fields

Nil

KPI Specific fields

Target KPI Value

How to Validate KPI

Suggested ways of working

• Ensure all check-ins and merge requests are properly timestamped.

• Ensure consistency in labeling or tagging check-ins and PRs for accurate data collection.

Sample JQLs

N/A

Benefits of KPI

How does the KPI help

The Number of Check-ins (commits) reflects both transparency and the effectiveness of task breakdown. A higher number of Check-Ins often indicates well-defined, manageable tasks.

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