Risk Cluster by Issue Type(3.3.9)

Risk is not uniformly distributed across all types of work. In some projects, Bugs carry the highest risk. In others, it is Stories or Tasks. This heatmap shows you the average risk score for every project-and-issue-type combination so you can see which work categories carry the highest scores.

What you can conclude

• A dark cell at a specific project-and-type combination means that kind of work carries higher risk scores in that project than elsewhere; a reviewer could ask what is different about how that work is handled there.
• A project that is dark across all issue types carries elevated scores in every type rather than in one, so the pattern is not specific to a kind of work.
• A project that is uniformly light carries low average scores across all work categories.

How this chart works

Heatmap with projects on one axis and issue types on the other. Cell color encodes average risk score for open issues in that combination. Darker cells indicate higher average risk. Each issue's score is the Composite Risk Score Ranking's, so its 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. Each ticket counts once, under the project and issue type of its latest event, so a ticket moved between projects is not also counted in the project it left.

What the date range selects

The only date this view carries is the week each issue was created, with no last-event counterpart, so the alive-in-window test the Composite Risk Score Ranking applies degrades to its upper half here. Only the end date applies, in whole weeks: issues created in a week that ends on or before it are included, as are issues from the week in progress when the range reaches it, and the start date does not narrow the heatmap. Older issues stay in their cells on purpose, because the risk scores behind the averages 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 stays empty rather than being filled in. Such issues still contribute to their project-and-issue-type cell, and are grouped by the week MetaFrazo first observed them, so the heatmap covers the pre-existing backlog instead of omitting it. The observation week says when the data starts, not when the work started.