Risk Score Distribution by Project(3.3.6)

A few high-risk issues are isolated cases. A project where most open issues carry elevated risk scores is showing a portfolio-wide pattern rather than a handful of exceptions. This visual shows you the distribution of risk scores across all open issues per project — so you can see not just whether a project has any risky issues, but whether risk is the exception or the norm.

What you can conclude

• A project with a high median risk score carries elevated risk across most of its backlog, not in a few issues — a reviewer would ask what the whole backlog has in common.
• A project with a low median but a high maximum score has isolated outliers — targeted intervention on specific issues is the right response.
• A project with zero critical-tier issues (score ≥80) has nothing in its open backlog above the critical threshold in this window.

How this chart works

Distribution chart showing risk score ranges per project by creation week: minimum, P25, median, P75, maximum, and count of critical-tier issues (score ≥80). Each project's bar describes the project as a whole: Median and P75 are the median and 75th percentile of the risk scores of all the project's open issues up to the end date, and Max is the highest of those scores. The scores are the Composite Risk Score Ranking's, so an issue's priority term reads the latest priority its events record, else, for an open issue whose events record none, the priority MetaFrazo read from Jira on the day it read it.

Which tickets count as open

A ticket counts as open when the latest status its events record is in Jira's To Do or In Progress category. A ticket deleted in Jira, or in a project moved to the trash or deleted, is not counted, and a ticket whose events record no status at all is left out. Tickets that have not changed status since MetaFrazo was installed are counted. A ticket moved to another project counts once, in the project of its latest event, so the tickets counted here are the ones the Composite Risk Score Ranking scores, on the same rule.

What the date range selects

This view carries one date per row — the week its issues were created — and no last-event counterpart, so the alive-in-window test the Composite Risk Score Ranking applies cannot be expressed here in full. Only the end date applies, in whole weeks: rows whose creation week ends on or before it are shown, as is the week in progress when the range reaches it, and the start date does not narrow the visual. Older creation weeks therefore stay visible, which is the intent, because the scores behind them are measured to the present moment.

Issues with no observed creation date

An issue that was already open when MetaFrazo was installed has no creation event, so its creation week cannot be computed and is left empty rather than filled in. Those rows show the week MetaFrazo first observed them in the Week column, marked "First seen" so it is not read as a creation week. They are not dropped. Each is grouped by the week MetaFrazo first observed it, so a pre-existing backlog appears as one row per observation week instead of one undated bucket, and the end date reaches it the same way it reaches every other row. Read those weeks as when the data starts, not as when the work started.