Nine flow metrics charts for your Jira dashboard. Pick a project or saved filter, and you're ready.
Delivery questions get answered every week, in planning meetings and status reports. Most answers are single dates and rough estimates, with no way to say how likely they are or what they're based on. The data that could back them up is already in Jira.
Each gadget answers one question you get asked about delivery. You'll find all of them under "Delivery Gadgets" when you add a gadget to a Jira dashboard.
Created vs. Resolved Chart
Backlogs rarely explode. They creep: a few more work items in than out, week after week. This chart puts created and resolved side by side, so you catch the trend while it's still small enough to act on.
Scope Change Chart
Scope always changes. The hard part is showing by how much. This chart starts with the open work at the beginning of your time window, adds what came in, subtracts what got done, bar by bar, and lands on today's total. "It keeps growing" becomes a number everyone can see.
Monte Carlo Forecast "When" Chart
A single date sounds precise, but it hides how likely it is. This forecast plays through 10,000 possible futures, based on how much your team actually finished per day or week, until the open work is done. You get a date for each probability from 5% to 95% and choose the one you're ready to commit to.
Monte Carlo Forecast "How Many" Chart
When the date is fixed, scope is the question. This table runs the same kind of simulation for a set number of weeks and shows how many work items your team can finish, with a probability attached to each number. So you decide what makes the cut before the deadline, not after.
Cycle Time Chart
Ask how long something takes, and you'll hear "about a week". That's true for some work items and far off for others. This chart plots finished work items by how long they took, with lines that show within how many days half, most or nearly all of them are finished. So "about a week" becomes "85% chance within 12 days".
Throughput Chart
Plans are built on how much a team should get done. This chart shows how much it actually does: the work items finished per day, week or month, with an optional trend line that shows whether the pace is holding. It's the same history the forecasts above are built on.
Work Item Age Chart
Late work rarely comes out of nowhere. It sits in progress, quietly getting older. This chart shows every started work item that's still open, by how long it has been underway and the stage it's in, against lines drawn from your finished work. An item above the 85% line is already taking longer than 85% of your finished work items did, and there's still time to step in.
Time in Status Chart
Work is often slow not because of the work, but because it waits: for review, for testing, for a decision. This chart breaks your finished work items down by time spent in each status, so you see where the time goes, which items took longest, and whether work is moving through a status faster or slower. You know where to start, and later, whether a change worked.
Work in Progress Chart
Ten things in progress feels productive. Usually it means each of them takes longer. This chart shows how many work items were in progress on each day, in total or per status, so you spot a rising line before it shows up in your cycle times.
Most charts need just one thing from you: which work items to look at, as a project or a saved filter. Two ask for a little more. The "When" forecast needs a second source for the open work, and Work Item Age needs your workflow stages in order. Everything else has a sensible default, from the time window to the percentile lines. You change it when you want to, not before the first chart appears.
Looking at several teams? Point a chart at a saved filter that covers them all, and it shows their work as one combined picture. Prefer each team on its own? Give each one its own chart.
Why so little to set up? Because the decisions that usually take the longest are already made. Here's which ones, and why.
Every chart follows the same few rules. They're fixed, so a number means the same thing on every chart and every dashboard.
Delivery Gadgets shows how work flows through a team, never how a single person performs. No chart breaks numbers down by assignee or filters work by person. That keeps the conversation on how the work flows, which is where delays usually come from, and off whoever happens to be in the room.
Got this page from a colleague? The short version:
Exactly what it reads and stores: Privacy Policy.
Delivery Gadgets for Jira Cloud is coming to the Atlassian Marketplace.