Versions Compared

Version Old Version 4 New Version 5
Changes made by

Ananth Pal

Ananth Pal

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Overview

Definition (Hover Text)

The Number of Check-In's reflects both transparency and the effectiveness of Check-ins & Merge requests helps in measuring the transparency as well the how well the tasks have been broken down. 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.

OR

The Number of Check-ins In's & Merge Requests Request's helps assess transparency and the effectiveness of task breakdown.

Source Tools

Github, Gitlab, Bitbucket, Azure Repo

Graph type

Line

Bar & Line

Filters

Branches

Hover Format on KPINumber

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

Fields on OverlayExplore

  • Project Name

  • Repository URL

  • Branch

  • Days/WeekWeeks

  • Developer

  • No. of Commit

  • No. of Merge

Business Logic

Calculation Formula

Count of number of PRs raised

Count of number of PRs merged

Trend

Increasing value is considered PR's (Pull Request's) raised during a period
Count of PR's (Pull Request's) merged during a period

Count of Check-In’s during a period
Count of Merge Request’s 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

27 MR’s

Check-In’s?

Configurations

Processor Fields

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

NUMBER OF MERGE REQUESTS when looked at along with commits highlights the efficiency of the review process