Datum

Apps → Linger

A Datum app for Jirav1.0.2

Linger

See how long issues sit in each status — time-in-status, cycle time and where work gets stuck.

Time in statusLinger · SPT-118
To Do 1d 4h
In Progress 3d 2h
In Review 5d 6h Stuck
See how long issues really sit — and where they stall.

The problem

'Why is this stuck?' is the most expensive question in Jira. Statuses fill up with issues that sit for weeks, but nobody can see which status is the graveyard — because Jira doesn't show time-in-status at all.

How it works

1

See the time in status

Open any issue and see exactly how long it has spent in each status — current and historical.

2

Find the bottleneck

Standard adds cross-project cycle-time and lead-time reports plus bottleneck detection, so the stuck status names itself.

3

Set the threshold

On Standard, define status SLA thresholds and get breach flags when work sits too long — then export the evidence.

A Datum app

the promise

Like every Datum app, Linger is Forge-native and runs inside your own Jira site — free for up to 10 users, with a single honest paid plan after. No separate sign-up, no data leaving your tenant. Why Datum →

Screenshots

Click any shot to view it full size.

FAQ

What's on the issue view for free?

Per-issue time-in-status — how long an issue has been in each status — free up to 10 users.

Cross-project view?

Standard includes cross-project cycle-time & lead-time reports, bottleneck detection and CSV export.

SLA-style thresholds?

Standard lets you set status SLA thresholds with breach flags — for the teams that run JSM-style SLAs on Jira work.

Works well with

Explore all Datum apps →

Guides

Best Jira time in status apps (2026) The best Jira time in status and cycle time apps compared for 2026 — what each measures, how they're priced, and which fits a small team or enterprise. How to see time in status in Jira Jira shows an issue's current status but not how long it has sat in each one. Here's how to see time in status — and spot the stage where work actually stalls. How to find bottlenecks in Jira Work piles up somewhere in every workflow. Here's how to find the status where Jira issues actually get stuck — not guess — using time-in-status. How to measure cycle time in Jira Jira's control chart is a start, but not a clear cycle-time number in real working hours. Here's how to measure cycle time and find where work actually waits. Jira Control Chart vs Cumulative Flow Diagram — which shows your bottleneck? Jira's Control Chart and Cumulative Flow Diagram get confused. Here's what each shows, what neither tells you, and how to find where work piles up. Jira's Control Chart vs time in status — how to actually find the bottleneck Jira's Control Chart gives one cycle time per issue on one board. Here's what it can't show, and how time-in-status reporting finds where work gets stuck. Cycle time vs lead time in Jira — what's the difference and how to measure them Cycle time and lead time ask different questions, and Jira measures neither cleanly. Here's what each means and how to get them from time-in-status.

Get Linger

Free for up to 10 users, with one honest paid plan after. See pricing →