Skip to content

Dwell

A Runs-on-Atlassian alternative to Timepiece for time in status

Timepiece is a mature, well-reviewed app with a large installed base. This page is not an argument that it is bad — it is an honest account of where Dwell differs, including the places Timepiece is the better choice.

Timepiece (by OBSS, formerly listed as “Time in Status”) and Dwell (by Hullara) both report how long Jira issues spend in each status, plus cycle and lead time. The practical differences for most teams are three: the hosting model, whether the report leads with averages or with median and p85, and what stays free.

The short version

What both do well

Both apps solve the same underlying gap: Jira records every status transition but never adds them up for you, so “how long did this sit in review?” has no native answer. Both replay the changelog to produce per-status durations, both aggregate across a project, both export to CSV, and both put a summary on a dashboard.

Timepiece has been doing it far longer, and the numbers show it: roughly 4,500 active installs and 269 reviews averaging 4.79 out of 5 when this page was written (August 2026). That is a strong record, and a brand-new app cannot claim anything comparable.

Where Dwell differs

Median and p85, not averages

An average cycle time is dragged around by whatever sat in the backlog for six months, and it tells you nothing about the tail your stakeholders actually notice. Dwell leads with the median (the typical issue) and p85 (the promise you can nearly always keep). Every report, trend and group-by is built on those two numbers rather than a mean.

Aging work in progress, flagged against your own p85

Dwell lists the open issues that have already been in progress longer than 85% of your finished work took. It is the one report that is about the future rather than the past: those are the issues about to become a problem, and you can still act on them.

Flow efficiency, blocked time, and time between any two statuses

Beyond per-status totals, Dwell reports what fraction of elapsed time was spent actively worked versus waiting in a queue, how long issues sit flagged as blocked, and the time between any two statuses you choose — Backlog to In Progress, say. These answer “where is the waste?” rather than “how long did each step take?”

The per-issue panel is free at any size

Dwell's freemium split is functional, not just seat-based: the time-in-status breakdown on an individual issue stays free no matter how large your site is. The paid part is the project reporting layer — the JQL reports, the trend, aging WIP, the histogram, group-by, the gadget and CSV. So a team can adopt the panel first and decide about reports later.

Runs on Atlassian

Dwell carries Atlassian's Runs on Atlassian badge: it runs and stores its index entirely inside your Atlassian cloud, with no external servers and no egress. Checked on the Marketplace in August 2026, Timepiece's listing does not carry that badge. That is a statement about where processing happens, not an accusation — plenty of excellent apps are hosted by their vendor, and it only matters if it matters to your security review. Verify it yourself on either listing before you decide; the method is in our page on data egress.

Where Timepiece is the better fit

Written plainly, because a comparison page that only flatters its own product is worth nothing to you.

  • Track record. 269 reviews at 4.79 stars, and thousands of teams already running it. Dwell is new and has none of that yet. If “has this been proven at scale?” is the question your organisation asks, Timepiece answers it and Dwell does not.
  • Cloud Fortified. Timepiece holds Atlassian's Cloud Fortified status, which covers operational maturity — reliability commitments, incident management, a bug bounty. Hullara does not hold it. If procurement asks for it, that is a genuine gap on our side.
  • Breadth. Its listing advertises a wider catalogue of report types and dashboard gadgets, plus AI assistance and automation actions. Dwell ships one gadget and no automation actions.
  • Try before installing. OBSS offers an online demo you can click through without touching your site. With Dwell you install it and look at the free panel.
  • Price at scale. Above roughly a thousand users Timepiece is cheaper per user — see the table below.

Pricing and the free tier

Both are sold through Atlassian with per-user monthly pricing, and both are free for sites of 10 users or fewer. Figures below were read from the Marketplace pricing API in August 2026; check current prices before you buy.

So price is not the reason to switch. Dwell is slightly cheaper for small and mid-sized teams and slightly dearer in one large band. Anyone arguing that a few cents per user should decide which reporting tool you run is selling you on the wrong axis.

Trying Dwell without leaving Timepiece

You do not have to choose to evaluate. Both apps read the same Jira changelog and neither writes to your issues, so running them side by side changes nothing about your data.

  • Install Dwell from the Marketplace. On first open of a project report it builds an index of your issue history, which takes a few minutes on a large project.
  • Open any issue and check the free panel — that is the whole free surface, at any team size.
  • Compare a project report against the same period in Timepiece. Expect the numbers to agree on per-status totals and to differ where one shows an average and the other a median: that difference is the point, not an error.
  • If you keep Dwell, uninstall Timepiece at your next billing boundary. If you do not, uninstall Dwell — nothing of yours left your tenant either way.

Questions

Also worth reading: Dwell compared with SaaSJet Time in Status · how to see time in status in Jira · the Dwell user guide.

Dwell is best for
Teams who want time in status alongside median and p85 cycle time, aging work-in-progress and flow efficiency, who want a per-issue panel that stays free at any team size, and who need the app to run inside their own Atlassian cloud with no data egress.
Timepiece is best for
Teams who want a proven, heavily reviewed app with a wider report and gadget catalogue, AI-assisted and automation features Dwell has not shipped, an online demo before installing, Cloud Fortified status for procurement — and a lower per-user price once you are past about a thousand users.
Bottom line
If no data egress or median/p85 flow metrics are your priority, try Dwell — the per-issue panel is free on every issue, so evaluating it costs nothing. If you depend on a Timepiece feature or need a long review history behind the app, stay put.

Questions

Is Dwell a drop-in replacement for Timepiece?
For per-status durations, cycle and lead time, group-by and CSV export, yes. For Timepiece's wider gadget catalogue, AI assistance and automation actions, no — Dwell does not have equivalents.
Will the numbers match what Timepiece shows?
Per-status totals should agree, since both replay the same changelog. Headline cycle time will differ if you compare Dwell's median or p85 against an average — those are different statistics, not different measurements.
Does Timepiece send data outside Atlassian?
We do not assert that. What is checkable is that its listing did not carry the Runs on Atlassian badge in August 2026, while Dwell's does. Where a vendor processes data is a question for that vendor's listing and documentation.
Can I run both at once?
Yes. Both are read-only with respect to your issues, so they do not interfere.
What happens to my data if I uninstall Dwell?
The index Dwell built is deleted with the app. It lived in Atlassian-hosted storage in your own tenant, and no copy exists anywhere else.
Get Dwell on the Atlassian Marketplace