Code Activities / Risks
Deep dive into your coding activities and delivery risks.
Purpose
This view is for team manger to see all the development activities and risks across teams and repositories. Moreover, extensive filtering can be used to slice and dice PRs across the organisation to follow the evidence and do quick investigations to validate standard process issues.
Improvement Actions: Logilica's pre-computed risk categories help to proactively manage PR processes before future problems, such as quality issues or delivery delays occur.
Explanations
Some of the information about each ticket in this report includes:
Code Size: The lines of code committed. While not a measure of productivity, it indicates complexity and effort for reviews, merges, etc. Large commits tend to result more often in delays.
Work Type: The predominant type of code changes in the PR — adding new code, reworking recently written code (one's own or others'), or maintaining older, established code.
Cycle time: The PR lifecycle time from the first commit to being merged/closed.
Breakdown: The lifecycle breakdown of each PR showing its Coding, Response, Review, and Integration time.
Updated: The last time the PR was touched as recorded by your git provider.
Status: Ticket status as defined by GitHub/GitLab, etc.
Risks
Logilica tracks the number of default risks for each ticket. This includes:
Stale: A PR that has been open but has not progressed from one stage to the next within a pre-defined time — it may be stuck waiting.
Long Running WIP: A PR that has been open without being merged for an extended period. This PR might be stuck or forgotten.
Risky Change: A PR that potentially deserves more attention because it is unusually large or far-reaching — for example changing a high number of lines, spanning many commits, or touching many files.
Complex Review: A PR that potentially deserves more attention because its review involved unusually high effort — for example a high volume of review comments, multiple review cycles, or several active reviewers.
Merged Outside Process: This identifies PRs that are merged, but did not follow a common quality process and were not reviewed or not approved.
Good to Know
The PR risks serve as predefined filters and can be combined with other existing or custom filters. Behind the More button on the filter bar additional complex queries such as below can be easily constructed.
Last updated