Guide · Jira Cloud
See how long Jira issues spend in each status
Aging WIP and stuck columns should not mean spreadsheet archaeology. Read durations from Jira’s own changelog — retroactive for existing work items — then review a project table, issue Activity, or a built report.
Try free when live · about USD 1.50/user/mo after ≤10 free · listing may still be pending Atlassian approval
App docs · try path01 — The gap
Why “how long in In Progress?” is hard in plain Jira
Boards show where work sits today. They do not answer how long it sat there, how many times it revisited a status, or which column is aging the backlog. Manual changelog digging and CSV exports burn time and go stale before the next standup.
02 — What buyers usually want
Status duration, aging WIP, and cycle views
- Time in each status from Jira’s native changelog — not a separate collector agent to install and babysit.
- Retroactive history so existing work items already have durations the moment you install.
- Project table for aging WIP across the board, not one issue at a time.
- Issue Activity so a single work item shows visits per status next to the rest of its history.
- Report builder for status, assignee, group, and period rollups when a one-off table is not enough.
03 — Tooling
Time in Status for Jira
Time in Status for Jira is a Forge app for Jira Cloud. Durations come from Jira’s own changelog. Intended design: compute on Atlassian Forge, customer data stays in your site / Forge storage — no external egress path. It is not a full BI warehouse; it is the status-duration and aging-WIP view for Cloud teams.
Marketplace listing: Time in Status for Jira (may still be in Atlassian review — the Marketplace URL is the source of truth). Product docs: /apps/time-in-status. Support: info@berkly.nl.