Overview | |
---|---|
Definition (Hover Text) | PR size value Size measures the number of source lines of code (also known as SLOC) affected by a pull request |
Source Tools | Github, Gitlab, Bitbucket, Azure Repo |
Graph type | LineY Axis - LOC X - Axis - Days/Weeks/Months |
FiltersBranch | Branches & Developers |
Hover Format on KPI<ABC> LOC | <From Date - To Date>: Lines |
Fields on OverlayExplore |
|
Business Logic | |
Calculation Formula | Physical SLOC ()LOCOption 1 - count of Source Lines of Code):
Logical SLOC (LLOC): Measures the number of executable statements in the source code. Source:
|
Trend | A decreasing trend is a +ve signconsidered positive |
Maturity Levels | TBD |
Instance level thresholds | 250 LOCNil |
Configurations | |
Processor Fields | Nil |
KPI Specific fields | NoneTarget KPI Value |
How to Validate KPI | |
Suggested ways of working | TBD |
Sample JQLs | N/A |
Benefits of KPI | |
How does the KPI help | The PR Size KPI helps by indicating the complexity and scope of changes in a pull request. It aids in managing review workload, as smaller PRs are easier to review, and larger ones may require more attention, reducing review delays and improving code quality. |
Content Comparison
General
Content
Integrations