Composite Risk Score Ranking(3.3.5)

Not all open issues are equally risky. A low-priority ticket that was created yesterday is very different from a high-priority ticket that has been reopened twice, hasn't moved in a month, and has had its priority escalated once already. This visual scores every open issue across five risk dimensions and ranks them so you can focus your attention on the ones that matter most.

The score is not a measure of complexity — it is a measure of governance risk. An issue with a high score has recorded several of the risk signals the score counts.

What you can conclude

• An issue scoring above 70 has recorded at least three of the five signals at once, because no two dimensions together can pass 55 points; a reviewer could ask who owns each one and what it is waiting on.
• A high score driven primarily by inactivity (long time since last event) means the issue has recorded no event for weeks; the score cannot tell a forgotten issue from one that was deliberately parked.
• A high score driven by reopen count and priority escalation together means the issue has come back out of a done status and has had its priority raised to High or above; the events show that it keeps returning, not why.

How this chart works

Ranked table showing all open issues scored 0–100 using a weighted formula: priority (up to 30 points: the latest priority the event stream records, else, for an open issue whose events record none, the priority MetaFrazo read from Jira on the day it read it; an issue with neither carries none), days since last event (up to 25), reopen count (up to 20), priority escalation count (up to 15), and a 10-point flag for tickets with only a single observed event.

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: the status an event shows the ticket in, or the status change it records. This includes tickets that have not changed status since MetaFrazo was installed. A ticket deleted in Jira, or in a project moved to the trash or deleted, is not listed, and a restored project brings its tickets back. A ticket whose events record no status at all is left out rather than guessed. A ticket moved to another project is one row, under its current key and project, and the Status column shows that latest status.

What the date range selects

The range is an overlap test, not a birth-date test: an issue is listed when it was created on or before the end date and its most recent event falls on or after the start date. That is deliberate. The score carries an inactivity term measured to the present moment, so the table is about risk as it stands today, and a long-lived issue that is still moving is exactly the row the ranking exists to surface; a filter on creation date alone would have hidden it.

Issues with no captured creation event

An issue that was already open when MetaFrazo was installed has no creation event in the stream. Its Created column shows the creation time Jira records on the issue's events instead, which is the issue's real creation date. Only an issue with neither a captured creation event nor a creation time on any of its events shows a dash; no date is invented. The row is still listed and still scored: none of the score dimensions depends on the creation date. What places a row with no captured creation event inside or outside the selected window is the date MetaFrazo first observed the issue. That date is an observation date, and reading it as an age is the one mistake to avoid: an issue first observed in the install week may be years old.