Flow Metrics

Find

Your teams, the trains they are on, your workflow stages and the aliases they match — and any work item, by its issue key or its type. An item opens straight into its editor.

Teams, ARTs & Stages

Teams

Each team keeps its own work items. The picker in the header chooses which one the dashboard is showing; Settings are shared by all of them.

Project id is the letters at the front of the team's issue keys — DAE for DAE-1552. It is what lets one export covering several teams be pasted in one go and split between them; it changes no figure. Leave it blank and the team simply takes nothing from a split.

Edit opens a team’s own settings — its WIP and 85% targets, whether it runs sprints, and whether it counts in the train’s aged share. Whatever a team has set is listed beside it, so the column reads down the list without opening anything.

Agile Release Trains

An Agile Release Train groups teams together. It is a label only — every figure is still worked out per team — and All Teams gains a picker for it. Teams need not be on one.

Statuses

Every status this app has read out of your exports, and the only words from a work system it keeps. Delete any you do not want; the items in it keep their dates and simply stop being grouped. The list holds at most 40.

Workflow Stages

A stage is a part of your workflow you want to measure the wait in — Build, Review, Test. Paste a Time in Status export with a column per status and each item's days land in the stage you have matched that status to. Several statuses can feed one stage: list them all and their days are added together. No export? Every stage you add here also gets a box on the work item form, so the days can simply be typed in.

The statuses come out of your export; the stages are yours. Paste an export with a Status column and the statuses in it are added to your list above, where you can see them and delete any you do not want. Grouping them into stages is optional — the work item age chart draws by status on its own — and a stage is worth adding when several statuses are really one part of your workflow, or when you want them in your own order. Change a grouping and every item you have already pasted moves with it; nothing needs re-pasting.

Ticking a status is enough. A status you have ticked into a stage also claims that status's column in a Time in Status export — so one tick does both jobs, and a set-up made by ticking needs nothing typed. A status nobody is currently sitting in still reaches your list, from the Days in … heading of its own column, so there is normally something to tick. The status names box is for what neither can reach: an old spelling your board has since renamed, or a status whose column heading was too long or oddly punctuated to be read as a name. Type those exactly as Jira spells them; capitals and punctuation don't matter, and a typed name wins where it disagrees with a tick.

Type the status, not the whole heading. A real export heads these columns Days in Code Review or Time in Code Review; the words in front are read off and the status inside is what has to match, so Code Review is the alias to type. It is also the spelling that matches a plain export's Status column, which the long one cannot. Leave Days in Done and Days Blocked out. The first keeps growing after the work has finished, and the second runs at the same time as whatever status the item is really in — neither is time spent in a stage.

Settings

Everything the charts depend on is here, and nothing else — a setting that changes nothing is worse than a missing one. Every one of them is shared by every team; the two figures a team sets for ITSELF are on its own row under Teams & Stages.

Labels & Work Types

The words on the charts, and what counts as a defect.

Anything whose Type is blank, or doesn't match the defect text above, counts as ordinary planned work.
Aged Work

How long something can sit unfinished before the app flags it.

Unfinished work only — nothing that has completed is ever counted here. Not the same as a team’s 85% ≤ target, which is checked against work that has finished; set each lower than that target so something is flagged while there is still time to act on it.

The feature box is empty by default, and empty is off — a fortnight is a rule about work items, and nothing here assumes it holds for features. Until you set a number, the Aged Work card in the feature view says so and shows what that team’s finished features actually took, so the number you pick is measured against your own board.

How much of a board may be aged before that is worth acting on is a question about a line you draw rather than about the threshold above, so it lives in Grading below, beside the other two scales that put a colour on a figure.

Grading

The lines you draw, and the only place in this app that puts a colour on a figure. All six boxes are empty until you fill them in.

Every pair is empty by default, and nothing is graded until both of its boxes are set — with either blank the figure is stated and the judgement is left to you, which is how every other figure in this app behaves. Set a pair and its tile takes a colour, a symbol and a spelled-out status, the Scorecard draws the three bands under the figure, and the aged share chart shades your bands behind its line. The first must be at or below the second — green above red is not a scale with its bands swapped, it is no scale, so nothing is graded until they are the other way round.

These are your boundaries, not the app’s. There is no number here worth assuming — a platform team carrying long spikes and a support team turning work over in a day would be handed the same verdict, and one of them would be wrong — and a line you had not agreed to would be a finding you never made. The two day boxes take the measure the Working Days switch below is set to, like every other figure in this app that is counted in days.

Features

Which rows are features rather than work items.

Separate them with commas, exactly as they appear in your Type column. Rows matching are kept apart from your work items, so no item-level figure moves. Feature ships here because it is what Jira calls the level above a Story — change it to whatever your board says, and clear the box to switch the whole feature layer off. Pair it with a Parent key column to join items to the features they belong to.

Your Week

Which day a week starts on — and so which day every weekly figure is read at the end of.

Our Sprint Cadence

How long a sprint is here, and the date one of them started — any one will do, and the app counts the rest off it. It measures nothing on its own: it is the grid the teams that run sprints are grouped on.

Calendar days, always — a two-week sprint is 14, and a ten-working-day one is 14 too. The working days setting changes how long an item is said to have taken; it cannot move a sprint boundary, because a boundary is a date on the calendar.

Working Days

Whether weekends count towards every figure measured in days.

Cycle time, lead time and the ageing threshold skip weekends — an item started on a Friday and finished on the Monday takes one day, not three. Public holidays are not known to this app and still count as working days, wherever you are.

Unusually Long Items

Whether one very long item is allowed to move your cycle time.

An ignored item still counts as delivered — throughput, net flow, the cumulative flow diagram, work in progress and the defect rate do not move. Only its cycle time, lead time and time in stage stop counting. Work that is still in progress is never ignored, however long it has been open, so the aged work figures are untouched.

Automatically ignores anything more than three interquartile ranges above the upper quartile of what finished in the window on screen — the standard test for an extreme outlier — and needs at least 12 finished items before it will offer an opinion. Narrowing the date picker changes what counts, because an outlier is only unusual next to the work beside it.

Most boards should leave this off. The median and 85% figures this dashboard leads with already shrug off a long tail — if one enormous item is spoiling the picture, the average is the only figure it is spoiling, and the median beside it is the better number to read.
Work Type Filter List

The choices in the Work Type filter on the dashboard. Display is what you pick; Value is the text matched against your Type column. Put several types in one row by separating them with commas — Story, Task is one choice covering both. Each is matched exactly, so Task does not pull in Sub-task. The arrows set the order the choices appear in the picker. Leave the All row alone — it means "no filter", which is why it is greyed out.

DisplayValue Actions

Back Up & Restore

One JSON file holding every team, their work items and your shared settings — a copy you keep, independent of this browser. It is the only copy of your data that exists anywhere else, so it is worth taking one.

Restoring replaces every team in this browser. You'll see what the file holds and be asked to confirm first. A backup file is also how you move your data to another device — download it here, and restore it there.

Start Again

Deletes every team and every work item in this browser. Your settings and your theme are kept.

Team Settings

Targets

WIP ≤ is how much work this team means to have open at once, and 85% ≤ how long it means an item to take — the promise the 85th percentile is read against. Both are drawn as a line on the charts and neither changes a figure: they are what the figures are compared to. Leave either blank and the app states the number without judging it.

85% ≤ is about work that has FINISHED; the separate ageing threshold in Settings is about work that has not. Different questions, so usually different numbers — and the threshold is normally the lower of the two, because an item past your target is too late to rescue. A promise of 10 days is often watched with a threshold around 6.

Sprints

Whether this team runs sprints, and on whose cadence. It changes no measurement — only where each period begins and ends, and whether Group by → Sprint is offered at all. A length here is in calendar days whatever the working-days setting says — a two-week sprint is 14 — because a sprint boundary is a date.

The Train’s Aged Share

Whether this team’s items count towards the Predictability figure on the Scorecard — every team is in unless you untick it. Untick one that measures its predictability another way, such as a Scrum team watching how much of its sprint commitment it completes, and the card says how many teams it is reading. Nothing else moves: not another tab, and not this team’s own dashboard.

ServiceNow Incidents

Whether this team’s ServiceNow Incidents count as defects — every team’s do unless you untick it. Untick it for a support team, whose incidents are mostly problems it solves for other teams: those items then leave its defect rate on its dashboard, on All Teams and on the Scorecard, and count as support work instead. Nothing else moves — they still count as delivered, and every other ServiceNow type is untouched.

Add a Work Item

An item needs at least one of those two. Leave Completed empty for work still in progress — it still counts as work started.

Delete All Data?

Clean Up Old Data

Choose how much history to keep. Nothing goes until you press Remove items — the summary below only says what that press would do.

How Much to Keep

Months count back from the newest item in the data, not from today — the same anchor the dashboard's date window uses, so a stale export is never one press from vanishing.

Which Teams
Unfinished Items

Off by default: an item with no completion date is still in progress, however old its start date.

Share a Read-Only Link

Anyone opening this link sees the figures you pick, with no way to change them and no sign-in. The data travels inside the link itself — it isn't uploaded anywhere, and it doesn't touch whatever they have saved in their own browser.

Which Teams
How Much History

Nothing is deleted — this only decides how much of your history rides in the link, which is what makes a long history shareable. Months count back from the newest item in the data, the same anchor the clean-up tool uses.

Your Link

If your paste had an issue key column, those keys travel in the link — they are what names the items on the charts, and a link without them would show a different picture from yours. Nothing else out of your work system does: no summaries, no statuses, no names.

This is a snapshot, frozen as it looks right now — later edits won't appear, so send a fresh link when the numbers move. There's no way to withdraw one once sent, so treat it like emailing a spreadsheet. If you trimmed the history, whoever opens it is told which date the copy starts from.