WIP Aging(2.4.11)

Open issues whose latest recorded status is in Jira's In Progress category, and how long each has been in that status — the issues actively aging against throughput. An issue deleted in Jira, or in a project moved to the trash or deleted, is not counted, and an issue whose events record no status at all is left out. WIP age counts from the recorded move into the current status; an issue whose move into its current status was not recorded has no WIP age and is not drawn. Older dots are colored more urgently. Click a dot to open the issue in Jira. Use the project filter to focus the view. The page's date range does not narrow this visual: it is a snapshot of everything currently in progress, so the longest-stuck issues stay visible under any range.

How this chart works

Scatter plot with five vertical columns, one per aging bucket (0–3 days, 3–7, 7–14, 14–30, 30+ days). Each bucket's longest-stuck issues (up to 24 per bucket) are drawn as individual dots — placed in its bucket column on the X axis, positioned by days in WIP on the Y axis, colored by bucket (green → amber → orange → red → dark red), and sized linearly with days in WIP (diameter 10–32 px). Dots within a column carry a small horizontal jitter so the drawn issues stay individually visible, and the legend prints every bucket's full issue count, so nothing outside the drawn set is hidden silently.

Hover any dot to see the issue key, days in WIP, priority, and the timestamp it entered its current status. Priority is the latest one the issue's events record, else, for an issue whose events record none, the priority MetaFrazo read from Jira on the day it read it; a dash means neither source supplied one. Click a dot to open the issue in Jira. A legend below the chart maps color to bucket and reminds you that size encodes age.