Plumbworks / Status Clock / Jira Cloud
Work is not slow. It is waiting somewhere specific.
Status Clock measures how long issues actually sit in each status, then puts it on a Jira dashboard. It answers the question a board cannot: not what is in progress, but what has been in progress for eleven days.
The useful finding is almost never the status people expected.
What you get on the dashboard
Five gadgets. Point each one at a board, a project, an epic, a release or any JQL query, and it keeps itself current.
- time in statusWhere the days go. Median and average duration per status, with the distribution behind it so one 90-day outlier does not distort your read.
- cycle timeFirst move to done. Cycle and lead time as a scatter with P50, P70 and P85 bands, so you can quote a delivery range instead of a single optimistic number.
- aging WIPWhat is stuck right now. Every open item plotted by how long it has been in flight, with thresholds you set turning amber and red.
- throughputItems finished per week. A run chart with a rolling median, which tells you far more about capacity than story points do.
- status historyThe trail for one issue. Every transition, who made it, and how long each leg took. Useful when someone asks why a ticket took a month.
- calendarsWorking time, not wall time. Weekends, public holidays and your own non-working days are excluded, per project if teams differ by region.
- breakdownSlice by anything. Assignee, issue type, priority, component, label, or any custom field, on every gadget.
- exportCSV out. Raw transition data for anyone who wants to do their own analysis in a spreadsheet.
Why this is a separate app
Most Jira reporting apps are large suites with thirty chart types and a configuration screen to match. Status Clock does one family of measurements and does it without a setup project.
Install it, drop a gadget on a dashboard, pick a board. There is no data model to define, no field mapping, and no onboarding call. If you later want burndown, velocity or Monte Carlo forecasting, buy an app that specialises in those instead of paying for a suite you use a tenth of.
Pricing
Billed by Atlassian at the same user tier as your largest Jira product. Free for instances of 10 users or fewer.
| Users | Per user / month | Monthly |
|---|---|---|
| 1 – 10 | free | $0 |
| 11 – 100 | $0.95 | $95 at 100 |
| 101 – 500 | $0.55 | $275 at 500 |
| 501 – 1,000 | $0.34 | $340 at 1,000 |
| 1,001 + | $0.21 | $420 at 2,000 |
Questions
Does it read history from before I installed it?
Yes. Status transitions live in Jira's own changelog, so the first scan backfills your existing history. You get useful charts on day one rather than in six weeks.
What happens when we rename or merge a status?
You map old statuses to new ones in settings, and historical data follows the mapping. Without that, every workflow change would reset your trend lines.
Can I exclude time an issue spent blocked?
Yes. Any status can be marked as non-counting, so "Blocked" or "Waiting on customer" can be held out of cycle time while still being measured separately.
Does it work with team-managed projects?
Yes, both team-managed and company-managed, including boards that draw from several projects.