Managing delivery across a cross-functional team means answering one question again and again: why did this slip? A release date keeps moving, standups keep confirming everything is "in progress," and nobody can point to the exact stage — design review, QA handoff, a dependency on another team — that's actually eating into the schedule. By the time the delay is visible in a retro, it has already cost the sprint. What a delivery lead needs is an Aging chart for Jira that shows where work is aging while it's still in motion, not a summary of what already went wrong. That's the gap Agile WIP Charts is built to close. Native Jira's Average Age Report tells you whether your backlog is trending older on average. Agile WIP Charts tells you which specific work items to unstick right now — and why they're stuck.
At a glance: native vs. Broken Build
What is WIP aging, and why do delivery leads track it?
"WIP" is work currently in progress — anything past Backlog and short of Done. Aging is simply how long an item has sat there without moving. Kanban practice, with its emphasis on visualizing and limiting work in progress, treats this as a live signal, not a retrospective one: a task that's been "in progress" three times longer than similar work usually takes is worth checking today, not next sprint.
This matters most to people who don't sit inside one team's daily standup. A Scrum master needs a fast visual for that standup itself, not a spreadsheet built the night before. A delivery or program manager overseeing several workstreams at once needs to know which one is quietly falling behind before it results in a missed date. An Agile coach or PMO consolidating trends across a portfolio of teams — the kind of view SAFe programs run on — needs the same signal, multiplied across boards. And a product or engineering lead reporting progress upward needs a chart that answers "are we on track" without an asterisk attached.
Jira gives every one of these roles two built-in tools for this job: the Average Age Report (available as a project report in company-managed projects) and the Average Age Gadget (available on dashboards). Both show the same single average.
What the research says about aging and flow
The principle behind WIP aging is a core tenet of flow-based delivery. The Kanban Pocket Guide defines work item age as one of four essential flow metrics alongside WIP, cycle time, and throughput — signals to inspect regularly so teams can intervene before aging work becomes a blocker.
ProKanban.org's practitioner guidance demonstrates how this works in practice: visualizing work item age on Jira boards with color thresholds tied to Service Level Expectations gives teams early warning to act — asking about blockers, swarming, or splitting work — before items exceed their expected cycle time.
The challenge for most Jira teams isn't understanding why aging matters — it's having a view that surfaces it without manual effort.
How to read Jira's native Average Age Report
The report lives under a company-managed project's Reports tab — you won't find it in team-managed projects at all. It plots a single bar chart showing the average age, in days, of every unresolved work item in the project, tracked over a period you choose.
How "age" is calculated: Jira measures from the work item's creation date to the end of each period (today, for the current bar). Every unresolved work item — regardless of status — counts toward the average. An work item sitting in Backlog for 30 days weighs the same as one stuck in Code Review for 30 days; the report can't tell you which is the problem.
Configuration options:
- Board — select which board's backlog filter to use (the filter defines which work items count)
- Period — hourly, daily, weekly, monthly, quarterly, or yearly granularity for each bar
- Days Previously — how far back the chart should reach (default 30)
The result is one bar per period, each representing that period's arithmetic mean. There's no distribution view, no outlier highlighting, and no way to drill into which work item is dragging the number up.
What it shows you:
- Work items unresolved — the count of open issues in each period
- Total age — the sum of ages across all unresolved items
- Average age per time period — the average age of everything still open
- A period selector (hour, day, week, month, quarter, year) and how many periods back to display
- A view over time, so you can see whether that average is climbing or holding steady
What it doesn't show you:
- Which status is actually holding the work
- Which specific work item is the outlier dragging the average up
- Any threshold for what counts as "too old" — every team has to eyeball that themselves
- A breakdown by team, epic, or label
- Anything beyond the one project or board you selected
This is an average across all unresolved work items, full stop. One badly stuck work item and nine perfectly healthy ones produce the exact same chart as ten mildly aging work items — the report has no way to tell you which situation you're actually looking at.
A quick example: Imagine your project has 10 unresolved work items. Nine of them have been open for 30 days each. One has been stuck in Review for 90 days. The Average Age Report shows 36 days — a number that masks the fact that you have one severely stalled item dragging the average up. You'd need to hunt through the backlog manually to find the 90-day outlier.
Where to find the WIP Aging chart by Broken Build
Agile WIP Charts installs from the Atlassian Marketplace. Once installed, add the WIP Aging (by status) chart to any Jira dashboard via the gadget picker, or embed it directly in Confluence pages. Unlike native reports, it lives where your team already works — no separate Reports tab to visit.
Where native Jira falls short on aging chart for Jira — and What Agile WIP Charts Adds
1. Daily average → Actionable to-do list
Native Jira: shows a daily average — useful for retrospectives, but you can't click a bar and see which items are the problem.
Agile WIP Charts: flips the question around: instead of "how has aging changed over time?" it answers "which items are in a red zone right now?" — so the reader closes the chart with a to-do list of work items to unstick, not just a trend line.
2. Arithmetic mean → Percentile-based health zones
Native Jira: shows one arithmetic mean and hides distribution — a small number of very old items can dominate the average without anyone noticing.
Agile WIP Charts: WIP Aging by status is a scatterplot with each dot as one in-progress work item, positioned by workflow stage and time in stage. Green / amber / red zones are drawn from your team's historical distribution: green ≤50%, amber 50-85%, red >85% of typical cycle time.
3. No stalled concept → Stalled-item rules
Native Jira: has no concept of a stalled item.
Agile WIP Charts: define per-status "if it hasn't moved in X days, flag it as stalled" thresholds — so work items sitting unnoticed in "Code Review" or "Blocked" surface immediately.
WIP Aging chart with stalled items highlighted in red — work items with no status change for more than 10 days.
4. Calendar time → Working-schedule-aware age
Native Jira: measures elapsed calendar time only — weekends and holidays inflate every work item's age.
Agile WIP Charts: configure time zone, working days, working hours, breaks, and holidays. Age is computed against actual working time, so weekends and holidays don't inflate every work item's age.
5. Undifferentiated bar → Per-status drill-down
Native Jira: lumps everything into one undifferentiated bar.
Agile WIP Charts: WIP Aging's default breakdown is by status — so you instantly see whether "old" means old-in-To-Do (backlog problem) or old-in-Code-Review (bottleneck problem). Regroup by board, project, issue type, epic, or assignee for deeper diagnosis.
WIP Breakdown panel — Expands to show distribution by status, issue type, project, or assignee for deeper diagnosis.
6. One bar chart → Three chart types
Native Jira: offers one bar chart.
Agile WIP Charts: WIP Aging by status (scatterplot for at-risk items), WIP Aging cumulative (cumulative aging view), and WIP Run chart (bar / stacked bar / line view of WIP quantity per period) — covering both "which items?" and "how much WIP?" questions.
7. No summary metrics → Health metric tiles
Native Jira: gives you a view over time and nothing else — no summary, no alert thresholds.
Agile WIP Charts: WIP age at a chosen percentile, count of items in the 85% red zone, count of stalled items — a full complementary read, not a single average.
8. One bar per period → Stacked bars by dimension
Native Jira: one undifferentiated bar per period.
WIP Run chart: see how WIP is distributed by issue type, team, priority, or any custom field. Spot uneven team load, focus shifts, or one type of work dominating.
9. Board filter only → Flexible issue filters
Native Jira: locks you to one board's saved filter.
WIP Run chart: let you decide what counts: filter by issue types, by specific epics, by releases across projects, or by custom JQL for full expressiveness (assignee, component, label, priority,exclude issues, and extended JQL functions from apps like ScriptRunner).
10. One board at a time → Multi-source scope
Native Jira: one board at a time.
Agile WIP Charts: multi-board, cross-project, releases, initiatives, epics, filters, JQL.
11. Reports tab only → Dashboards and Confluence
Native Jira: chart is trapped on the project's Reports tab.
Agile WIP Charts: embed interactively into Jira dashboards and Confluence pages via Smart Links — filters, grouping, and calculations stay editable inside Confluence. CSV / PNG / PDF export.
In practice, this is the difference in one sentence: Agile WIP Charts helps teams identify aging or stalled work and investigate it at work item level — the exact step where the native report hands off to guesswork.
When the Average Age Report stops being enough
If any of these sound familiar, the native report is probably costing you more time than it saves:
- You've asked, "Which specific work item is dragging this average up?" and had to hunt for it manually.
- You manage multiple boards or teams and want a consolidated view instead of switching between tabs.
- Your team already has a rough sense of "normal" cycle time and wants that turned into an actual threshold, not a gut check.
- You need this chart on a dashboard or a Confluence status page, not just as a tab within a single project.
- You're reporting upward, and "average age is 4 days" isn't a good enough answer to "where exactly are we behind."
See WIP Aging charts on live examples
Rather than take this on faith, explore these interactive examples on sample data:
- WIP Aging Chart — combines boards, projects, epics, or JQL into one chart with percentile zones and a breakdown by any Jira field.
- Kanban WIP Aging chart — tracks flow across Kanban boards and flags stalled items in review or testing.
- Sprint Aging chart — shows which sprint items risk missing the commitment, across one or several Scrum boards.
Each example runs on sample data, so you can check health zones, breakdowns, and (in the Kanban example) stalled-work highlighting before you install anything.
Four playbooks for WIP Aging charts
Each playbook answers a specific question. Pick the one that matches what you're trying to do, configure the chart accordingly, and use the readings to drive your next action.
1. Catch at-risk work early
Question: Which items are likely to miss their SLA or commitment?
Setup: Turn on percentile zones and choose which lines to show (P50, P70, P85, P95). Thresholds are calculated from completed issues over the selected interval.
Reading: Dots in the amber zone (85–95%) are older than most past work and approaching the upper limit. Dots in the red zone (above 95%) have exceeded it and are unlikely to finish within the expected time. Hover a dot to see its key, assignee, and time spent in each stage.
Action: Escalate or swarm red items first, then review amber ones. Check whether they are blocked, under-resourced, or out of scope, then split them or move them to an expedite lane.
Enable Highlights to color-code issues by percentile zones. Hover any dot to see its total age, time in each status, and whether it breaches the 85% or 95% threshold. Red-zone items need immediate attention.
2. Drive daily triage
Question: Which items should the team discuss first at today’s stand-up?
Setup: Sort the issue list by WIP age column. Open the issue list to see each item’s age and the date of its last status change.
Reading: Items with the highest age or the longest time since the last move need attention first, especially those near or above the 85th percentile.
Action: Start the stand-up with the oldest items. Ask what is blocking them, whether the scope has changed, and whether someone else should take them over.
Configure stalled issue detection to surface work stuck in a status. Set the threshold (e.g., 10 days), filter to show only stalled items, and sort the issue list by WIP age to prioritize your daily triage.
3. Expose hidden waiting
Question: Where is work waiting on a handoff or an external dependency?
Setup: Turn on Stalled issues and set a threshold. Items that exceed it highlight in red. To highlight blocked items, apply filters, for example by label or custom field.
Reading: A cluster of stalled dots in one column points to a bottleneck at that stage. If stalled items appear across several stages, the cause is more likely systemic external dependencies than a single slow step.
Action: Find out why the items are waiting. Depending on the cause, engage the team that blocks them, request resources or automate approvals. Then shorten handoff queues and adjust WIP limits.
Set how many days without a status change mark an item as stalled, and choose how stalled items appear on the chart, for example highlighted in red. Enable Stalled issues in the Health metrics menu to show their count above the chart.
4. Align clocks and policies
Question: Which clock should define “too old” for each class of service?
Setup: In the Calculation setting, choose how age is counted: from issue creation, from the first WIP status, from entry into the current stage, or as active working time. Turn percentiles on or off to match your policy.
Reading: Creation age includes time in the backlog, flow age starts when work begins, stage age resets on every status change, and active time counts only periods of active work. Switching clocks changes where items sit relative to the percentile lines.
Action: Agree with stakeholders on which clock drives the SLA. If you use flow or stage age, track backlog age separately, and apply the same settings across teams for consistent comparisons.
Choose which statuses count toward WIP age. By default, only In Progress statuses are included (flow time). Enable To Do statuses to reveal how long items waited before work began.
When the native report is enough — and when it isn't
The core difference: Native Jira's Average Age Report answers a retrospective question: "has the average age of unresolved work items trended up or down over the last N days?" It's one arithmetic mean per day, on one board, with no distribution view, no drill-down, and no way to flag which specific items are dragging the mean up. Agile WIP Charts answers a different, action-oriented question: "which items should I move on right now?" — with percentile-based aging zones, stalled-item rules, working-schedule-aware age, breakdown by status, and drill-down to the exact work items in trouble.
For a single, small, well-understood project, the Average Age Report can genuinely be enough: if the whole team already knows what "normal" looks like and nobody else needs the number, a simple average is a fine sanity check.
It stops being enough the moment more than one person needs to act on it. A Scrum master needs to know which card to raise in standup, not just that the average moved. A PMO needs the same signal rolled up across a program. A product lead reporting upward needs a number with a reason already attached. That's the difference between an average and an investigation — and it's the gap Agile WIP Charts is built to close.
Part of the Agile Reports & Gadgets suite
WIP Aging charts are part of Agile Reports and Gadgets — a bundle that includes velocity charts, burnup/burndown forecasting, cycle time analysis, cumulative flow diagrams, and more. All charts share the same configuration patterns: flexible data sources (boards, projects, JQL, releases), customizable calculations, and export to CSV, PNG, or PDF.
The bundle runs on Jira Cloud (Forge-native) and is free for teams up to 10 users, with a 30-day trial for larger teams — no credit card required.
FAQ
Does Jira show the age of work in each status, not just overall?
Not natively. The Average Age Report provides a single project-wide figure. Per-status aging requires Agile WIP Charts.
Is the Average Age Report available on every Jira project?
No — it's a classic report available only in company-managed projects (formerly "classic projects"). Team-managed projects don't have access to the Average Age Report or Control Chart. If you're on a team-managed project and need aging visibility, a Marketplace app like Agile WIP Charts is your only option.
What counts as a "stalled" work item?
Native Jira doesn't define one. Agile WIP Charts lets you set a stalled threshold (for example, no status change in 10 days) in the Stalled issues settings. Health zones are a separate feature, configured in the Highlights menu using percentiles from your completed issues.
Can I see aging data across multiple teams in one view?
Not with the native report, which is scoped to one board or project. Agile WIP Charts can pull from multiple boards, teams, or a JQL filter into a single chart.
Do I need to install anything to see how this works?
No — the interactive example is live on a populated board; no install required.
.png)
