Agile WIP Charts adds WIP aging and flow diagnostic charts to Jira Cloud. The WIP Aging chart – the app's core view – shows how long each in-progress issue has spent in each workflow status, so scrum masters and delivery managers can spot aging work during standup and daily triage.
You know the moment in standup: someone asks "which work items are stuck?" and you open the WIP Aging chart. Each item shows time broken down by status – In Development, Code Review, Testing – but the real question is simpler: is this item taking too long overall? With the previous chart, you had to add up status columns mentally and compare the sum against your team's cycle time threshold. And if the columns were in alphabetical order instead of workflow order, the left-to-right diagonal pattern that signals healthy flow was scrambled before you started reading.
The new Aging Cumulative chart answers the "too long overall?" question directly. Each dot represents one in-progress item. The y-axis shows total time that item has spent across all selected WIP statuses combined – not broken down by stage, just the cumulative number your team actually debates in triage.
Horizontal reference lines mark the team's 50th, 85th, and 95th percentile cycle time, each labeled with the actual value in the selected unit (e.g. 5.59 days, 17.15 days, 47.94 days). Items sitting above the 85th percentile line have been in progress longer than 85% of historically completed work. That is the signal – no spreadsheet, no mental addition.
A chart type selector above the chart lets you switch between Aging Cumulative and Aging By Status without reconfiguring filters or losing your data source settings.
Below the chart, the Breakdown groups items by risk zone – less than 50%, 50%–85%, 85%–95%, and above 95% of historical cycle time – so you can see at a glance how many items fall into each zone. Click into a zone to see the item list with key, summary, assignee, WIP age, and per-status time.
The Aging chart previously displayed workflow columns in alphabetical order. For a team whose process flows from "In Development" through "Code Review" to "Testing", alphabetical ordering puts "Code Review" before "In Development" – destroying the visual diagnostic that makes aging charts useful.
You can now drag statuses in the Statuses menu to set the column order. Define the sequence once, and both chart types (Aging By Status and Aging Cumulative) follow your actual workflow left to right.
The statuses available in the reordering list come from the Custom WIP statuses defined in your Calculation settings.
Standup triage shouldn't start with mental arithmetic. With cumulative aging and workflow-ordered columns, the items that need your team's attention surface the moment you open the chart – ranked by risk, compared against your own benchmarks, in the order work actually flows.
👉 Evaluate Agile WIP Charts on the Atlassian Marketplace
Both features are also available in Agile Reports and Gadgets 9.3.0 (released 20 Jul 2026) for teams already using the reporting suite.
From the Broken Build team behind Agile WIP Charts
Vasyl Krokha _Broken Build_
0 comments