Content Comparison

Definition (Hover Text)

The Number number of Check-In's Ins (commits) & Merge Request's that are merged helps assess and Merged Pull Requests (Merge Requests) helps evaluate transparency and the effectiveness efficiency 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 CommitCheck-ins

• No. of Merge Requests

Business Logic

Calculation Formula

Count of Check-In’s Ins (commits) during a period
Count of Merge Request’s merged 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

Check-Ins - In’s ?
27 MR’sMerged Pull Requests - 333

Configurations

Processor Fields

N/A

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

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