Overview | |
|---|---|
Definition (Hover Text) | Number of Check-ins & Merge requests helps in measuring the transparency as well the how well the tasks have been broken down. The Number of Check-ins & Merge Requests 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 KPI | Number of Check-ins: XX |
Fields on Overlay |
|
Business Logic | |
Calculation Formula | Count of number of PRs raised Count of number of PRs merged |
Trend | Increasing value is considered a positive trend |
Maturity Levels | M1: 0-2 M2: 2-4 M3: 4-8 M4: 8-16 M5: >16 |
Instance level thresholds | |
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 |
General
Content
Integrations