Last updated: October 18, 2026
Switching to StatusPulse from another time-in-status app
There is nothing to import
Time in status is worked out from each issue's own history in Jira. StatusPulse reads that history the first time you run a report, so every issue you ever had is already measured. You do not export anything from your old app, and you lose nothing by uninstalling it later.
What does not carry over is the old app's settings: which query you ran and how time was counted. Start from a preset, at the top of the StatusPulse page, sets those in one step. A preset sets only the query and how time is counted. It never changes your timezone, working week, day or holidays. Press Run report, then Save these settings to keep it. The dashboard gadget uses whatever you saved.
| Preset | Query | Counts |
|---|---|---|
| Working hours, every issue (the StatusPulse default) | order by created DESC | your working hours |
| Calendar time (24/7), open issues: how long each has sat in its current status | statusCategory != Done ORDER BY updated DESC | every hour, nights and weekends included |
| Calendar time (24/7), every issue | order by created DESC | every hour |
Coming from Issue Time in Status (GTOLA)
That app shows, on each issue, how long it has been in its current status, adding up earlier visits to the same status, and the time in other statuses when you click it.
- Use the preset Calendar time (24/7), open issues: how long each has sat in its current status.
- Their glance number is StatusPulse's Current status, all visits column in the By issue table. Time in current status is the visit in progress only. The two differ once an issue has come back to a status.
- Their per-status breakdown for one issue is in the CSV export, which has one row per issue per status. To look at a single issue, put
key = ABC-123in the query. - What is different: StatusPulse is a report page and a dashboard gadget, not a panel on the issue. You get the same numbers for every issue in a query at once, plus the median, the 85th percentile, cycle time and SLA targets.
Coming from Pivot Report (Colined)
Pivot Report is a pivot-table and roll-up tool: epics and custom hierarchies, worklogs, capacity, Excel and Confluence export. Time in status is one part of it. StatusPulse replaces only that part. If you use Pivot Report for epic roll-ups or worklogs, keep it.
For the time-in-status part, start with Calendar time (24/7), every issue and the same JQL filter your pivot used. Then switch Measure to Working hours if you want nights and weekends left out.
Checking the numbers side by side
Run both apps on the same query before you uninstall anything. Differences have three usual causes:
- Working hours versus calendar time. Set StatusPulse to Calendar time to compare like with like.
- Long-lived issues. Jira returns only the most recent part of a long changelog with a search. StatusPulse marks those rows partial history and counts from the oldest change it received, so its total is a lower bound rather than a guess.
- Renamed statuses. StatusPulse keeps a renamed status as one row. Apps that go by the name alone show it twice.
If a number still disagrees, send the query and one issue key from the support page.
What StatusPulse does not do
There is no issue-view panel, no epic roll-up, no worklog reporting, no Excel file (CSV instead) and no scheduled email. If you need one of these every day, StatusPulse is not a full replacement yet.