Open Issue Age Distribution(4.2.7)

An issue in the 90+ band was created more than 90 days ago and is in a To Do or In Progress status now; it may have been closed and reopened in between. It may be work that is still wanted and waiting, a problem not yet solved, or an item nobody has closed; the events show its age and its current status, not which of these it is. The age bands show when open work was created, not how much of it there is; the count in each cell shows the amount.

This heatmap shows the age distribution of open issues across all projects so you can see at a glance where the oldest open work is concentrated.

What you can conclude

• A project with a large proportion of issues in the 90+ day bucket is holding issues created months ago that are open now; a reviewer could ask which of them are still wanted.
• In a project where most open issues are fresh (0–7 days), most of its open work arrived in the last week.
• A portfolio where the 90+ day bucket is large across multiple projects at once holds old work across the organization, not in one team.

How this chart works

Heatmap showing issue counts per age bucket (0–7 days, 8–30 days, 31–90 days, 90+ days) per project. Darker cells indicate more issues in that age category. The project filter applies and the date range does not: the heatmap is a snapshot of the issues open now, aged up to today, so there is no period for a date range to select.

An issue counts as open when its latest recorded status is in Jira's To Do or In Progress category; deleted issues, issues whose latest recorded status is in the Done category (including issues closed before MetaFrazo began receiving events), issues with no recorded status, and issues in a project that was moved to the trash or deleted and not restored are not counted.

Age runs from the creation time Jira records for each issue, so an issue created before MetaFrazo began receiving events lands in the bucket of its real age. An issue whose recorded events carry no creation time is aged from the first event MetaFrazo recorded for it, which makes its age a minimum. For every issue with a recorded creation time this is the age the SLA Breach Probability per Open Issue table uses.