Tagline: Time in every status, on a working calendar that is right about weekends, holidays and daylight saving — plus a real SLA engine with pause and breach. Free to 10 users, then $0.62.
Install from the Marketplace listing, or in Jira go to Apps → Explore more apps and search for Status Clock. You need to be a Jira administrator. It starts working immediately — it reads history Jira already keeps, so there is no waiting period before numbers appear.
Add the Time in Status (Status Clock) or SLA Compliance (Status Clock) gadgets to a dashboard: Dashboards → Add gadget → search Status Clock.
Status Clock replays each issue’s own Jira history to work out how long it spent in every status, in every person’s hands and in every sprint, and measures it on a working calendar your team defines — several shifts a day, different hours per weekday, holidays and half days, per project. Then it does the thing the time-in-status apps do not do: it runs your SLAs on the same clock, with start, pause and stop conditions, targets by issue type and priority, and breach and at-risk detection.
It runs entirely on Atlassian’s infrastructure. No data leaves.
Time in status, told honestly - Time in every status, per issue and aggregated, as elapsed time or as working time. - Count, total, average, median, P85 and P95 on every row — because a mean of six days over a sample where one issue sat in Blocked for a year is not a fact about your team. - How many times each issue re-entered each status, and how long the first visit, the last visit and the average visit took. - When each issue first reached, and last left, each status. - Transition counts per status pair, with backwards moves marked: that is where your rework is. - Lead time and cycle time, and any pair of statuses you want timed. - Time per assignee, per team, and per sprint — clipped to the sprint’s own life, so an issue dragged into next month’s sprint has not been in it for a month.
Working calendars that are actually right - A week is seven days of intervals, so a lunch break is a gap and Friday can end at one o’clock. - Public holidays, and named dates with their own hours for a half day. - A calendar per project. Two teams in two countries, measured on their own clocks, in one report. Nobody else in this category does this. - Daylight saving handled by construction: a working day is eight hours whichever Sunday it follows, and calendar time reports the elapsed reality. Pinned by tests against a minute-by-minute reference implementation. - “1 day” means one of your days. Nine working hours on an eight-hour calendar reads “1d 1h”, not “9h”.
SLA for Jira Software, not just Service Management - Start, pause and stop on: created, entered a status, is in a status, status category, resolution set or cleared, assignee set or cleared, priority, or any field changing. - Targets that differ by issue type and priority inside one SLA, so a tier ladder does not need one SLA per tier. - Each SLA measures on its own calendar. Critical on 24/7 and the rest on business hours does not mean two SLAs. - Breach, at risk, running, paused, met — with the elapsed time, the time left, and a due date worked out on the calendar, so an SLA started at four on Friday afternoon is due on Monday morning and not at eight on Friday evening. - Restart on re-entry, or measure once. Your choice, per SLA.
Find it in ordinary Jira search No custom fields. No screens to configure. No thousands of update notifications. The app writes one issue property, and Jira indexes and sorts it:
tisSlaState = "breached"
tisSlaBreaches > 0
tisSlaDueAt < endOfDay()
tisStatusAge > 48
tisCycleTime > 40 ORDER BY tisCycleTime DESC
Add a label on breach and Jira Automation has a native trigger to hang a rule on — notify Slack, escalate the priority, page someone. It is added once, on the transition into breach, never on every re-check.
Reports you can actually move around - By status, grouped, two-dimensional pivot, per issue, over time, transitions, entry and exit dates, and SLA compliance. - Group by assignee, team, issue type, priority, project, epic, sprint, status, label, component, fix version or resolution. - Bar, stacked bar, pie, line and a histogram, on any report. - Conditional highlighting, multi-column sorting, and a summary row on every table. - CSV export with a configurable field separator and decimal mark, at full precision, carrying every measured value — so it opens correctly in a German or Brazilian Excel and you can do arithmetic on it.
Fast, and honest about it Issues are read once and aggregated many times. Changing the report, the grouping, the metric, the statistic, the unit, the sort or the chart redraws immediately without reading Jira again. Reading is paged with a progress count, so the numbers fill in as they arrive instead of hiding behind a spinner, and there is no hidden ceiling that turns into a timeout.
Show your work The issue panel lists every segment of that issue’s life — the status, when it started, when it ended, and what it came to on the calendar — and the segments add up to the total in front of you. If you ever wonder where a number came from, it is one click away.
Where it lives A global page, a project page, an issue panel, and two dashboard gadgets.
Free for up to 10 users. $0.62 per user per month after that, falling with size. One edition; everything on this page is in it.
At 100 users that is $55 a month against $115 for SaaSJet Time in Status, $120 for OBSS Timepiece and $182 for Time to SLA — and those are three apps where this is one. A team that wants time-in-status and SLA today buys two of them.