Zero-Comment Solo-Close Heatmap(JIRA:4.2.9)
VisualClosures 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 zero-comment solo-close rate for every project-and-issue-type combination it draws (at most twelve projects by name, see below), 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 zero-comment solo-close 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.
How far back it reads
The heatmap reads at most the last 92 days, a calendar quarter, of the selected range, ending on the range's last day or today, whichever is earlier. A range that starts within those 92 days is read whole. For a longer range, or one with no start date, it counts the weeks of those 92 days, and the panel says so beside its title. To review an earlier period, end the range there. This keeps the read within the panel's row limit however many projects the organization adds.
Which projects are drawn
With no project picked, the heatmap draws a row for at most twelve projects: of the projects with at least 10 delivered closures by people in the range, the twelve with the highest zero-comment solo-close rate across every issue type taken together, their people's qualifying closures over their people's delivered closures, the rule of a cell applied to the whole row. Ties go to the project key that sorts first. A share resting on fewer closures is decided by one or two of them (one closure reads 0% or 100%), so a project under that floor never takes one of the twelve places, however high its share; its closures are counted in the Other projects row. The rate's parts add up, so every other project is drawn as one gray Other projects row: at each issue type, the other projects' qualifying closures over their delivered closures taken together, so a project with more closures weighs more. Its cells are gray and carry no color threshold, because each stands for several projects, not one. Pick a project in the filter to see its own row at any time, whatever its volume; with twelve projects or fewer at or above the floor every one of them is drawn, and there is an Other projects row only for the projects under it.
The closures behind a cell
Click a cell to list the closures its rate counts, latest first: the issue, its week, when it was delivered and the account that closed it. Each one had no recorded comment and was closed by the person who created it. The list covers the same weeks as the heatmap and adds up to the closures the cell's tooltip names. The Other projects row opens no list; pick a project in the filter to list its closures.
Account column: the rows are listed for every role that can open this panel, but the account behind each row is shown only after an organization owner turns on "Show person-level views" in Organizational Settings, and then only to owners and admins. Otherwise the column, the export and AI answers about this list withhold people's account ids, and the column reads Hidden; app accounts stay named.