Backlog Age Distribution(2.4.5)
VisualA large backlog is one thing. A backlog full of tickets that have not changed status in weeks is another. This visual breaks the open backlog in each project down by how long each ticket has gone without a status change, so you can see not just how big the backlog is but how much of it has stopped moving.
Fresh issues (0–7 days) arrived or changed status recently. Frozen issues (30+ days) have not changed status in over a month; the events show how long they have waited, not whether the work is still wanted.
What you can conclude
- A large frozen bucket means many open to-do tickets have not changed status in over a month; a reviewer could ask which of them are still wanted.
- If frozen issues dominate a specific project, the waiting work is concentrated there rather than spread across the portfolio.
- A backlog where most issues are fresh (0–14 days) holds work that arrived or changed status in the last two weeks.
How this chart works
Stacked bar chart grouping the open issues in a To Do-category status by age, across four buckets: fresh (0–7 days), aging (8–14 days), stale (15–30 days), and frozen (30+ days). Grouped by project. The Y-axis shows absolute issue counts. Each segment is labeled with its count directly. Issues in an In Progress-category status are not counted here.
An issue counts as open when the latest status its events record is in Jira's To Do category. Deleted issues, issues in a project that was moved to the trash or deleted and not restored, and issues whose events record no status that maps to a Jira status category are not counted, and an issue that moved between projects counts once, under its current project.
Age runs from the issue's latest captured status change. An issue whose status never changed while MetaFrazo was receiving events is aged from the creation time Jira records for it, so an issue that last moved before then, and never since, shows an age longer than its real time in its status. An issue with neither a captured status change nor a recorded creation time is left out, because its age is unknown.
When frozen issues represent more than 50% of open issues in any project, an amber warning banner is shown above the chart.
The page's start date does not narrow this chart. Each project carries a single recency date, the most recent point from which one of its issues is aged (a status change, or the creation of an issue never moved since), and the age buckets are measured to the present moment, so a lower bound on that date would delete exactly the projects whose backlog has gone longest without a status change, which is the population an age distribution exists to show. The end date still applies to that recency date, so a range ending in the past leaves out every project whose most recent status change, or most recent creation of a never-moved issue, came after it, together with all of that project's older issues. Use the project filter to focus on a specific team.