> For the complete documentation index, see [llms.txt](https://docs.logilica.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.logilica.com/metrics-and-reports/code/code-activities-risks.md). # Code Activities / 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. {% hint style="success" %} **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. {% endhint %} ## 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.

Additional PR filters to slice & dice

--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.logilica.com/metrics-and-reports/code/code-activities-risks.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.