Missing Approval Heatmap(5.2.9)

Closures with no recorded comment that were closed by their own creator can cluster in particular kinds of work: in one project in Bugs, in another in Tasks or Stories. This heatmap shows the missing-approval rate for every project-and-issue-type combination, the share of delivered closures that were both zero-comment and single-actor: no comment other than one posted by an app or a service-desk customer appears in the issue's recorded Jira history, and the person who closed it also created it. It shows where that pattern concentrates, so you can see where to start asking how review is recorded.

What you can conclude

• A dark cell marks one kind of work in one project where a large share of delivered closures, 30% or more in a red cell, had no recorded comment and were closed by their creator. A reviewer could ask how review is recorded for that kind of work in that team, and whether it is work the team expects to close on its own.
• A project that is dark across all issue types shows the pattern across its work rather than in one type, so the question concerns how that project's workflow records review as a whole.
• A uniformly light heatmap means few delivered closures combine the two signals; it does not show what any recorded comments contain.

How this chart works

Heatmap with projects on one axis and issue types on the other. Cell color encodes the missing-approval rate: closures that were both zero-comment and single-actor, as a percentage of delivered closures for that combination. Delivered and qualifying closures are also recorded by the closer's account type (person, app, customer, unknown, erased, or system where no closer was recorded); the types add up to each count. Closures into abandoned-classified statuses are backlog hygiene and are not counted; a cell with no delivered closures shows no rate rather than a zero. Thresholds: green <10%, amber 10–20%, orange 20–30%, red ≥30%.

Each delivered closure is attributed to the type of account that closed it, as Jira reports it. The rate covers closures made by people's accounts; an app account such as Automation for Jira that closes issues it created is recorded as app activity and shown beside the rate, not inside it, and closures by service-desk customers, by accounts Jira returned no type for and by erased accounts are shown the same way. A comment posted by an app or a service-desk customer does not count as a recorded comment, so it leaves the closure zero-comment. A comment by any other account counts, including one by an account Jira returned no type for, one by an erased account and one with no recorded actor, because any of them may be a person's. An action Jira records under a person's account counts as that person's, even when a tool acted on their behalf.