Dwel — Time in Status for Jira

by Better Integrations

works with Jira Cloud

OVERALL RATINGS
INSTALLS
SUPPORT: Partner Supported
TRUST SIGNALS

Showing details for Cloud

Overview

Reviews

Pricing

Privacy & Security

Support

Installation

Similar Apps

New

Key highlights of the appTime in status, ageing, cycle & lead time reports for Jira. Audit every number, export to CSV. Free up to 10 users

More details

Where does the time actually go? Dwel answers that, and shows its working.

Eight reports: Time in Status, Time per Assignee, Cycle and Lead Time, Status Count, Transition Count, Trend, Status Ageing (the average age report), Status Entrance Date.
Audit any figure. Click a duration to see the changelog transitions behind it: entry and exit timestamps, the assignee at each, the arithmetic.
Working-hours calendars: your business hours, 24/7, or Jira's own time-tracking units. Every duration says which it used.
Four charts: workflow bottlenecks, ageing WIP, cycle-time scatter, status trend. Export to CSV, Markdown or PNG.
Five surfaces in Jira, 50,000 issues per report, and imports from Bloompeak Time in Status.
Free up to 10 users — every report, chart and export. Above that, a 30-day trial, no card.
Runs on Atlassian: a pure Forge app with no outbound network requests, so your Jira data never leaves Atlassian's infrastructure. English only.

Resources

App documentation
Comprehensive set of documentation from the partner on how this app works

Privacy and Security

Privacy and security questionnaire has been filled by the partner

Privacy policy

Atlassian's privacy policy is not applicable to the use of this app. Please refer to the privacy policy provided by this app's partner.

Partner privacy policy

Security program

This app is not part of the Marketplace Bug Bounty program.

Integration permissions

Dwel — Time in Status for Jira integrates with your Atlassian app

Version information

Version 2.1.0•for Jira Cloud

Release date: Aug 16th 2026
Summary: Cycle & lead time across status groups, faster reports on large projects.
Details: Cycle & Lead Time now spans status groups you define, so a "cycle" can be several statuses treated as one phase rather than a single start and end status. Reports over large projects read status history in fewer passes, cutting the time to first row on 50,000-issue scopes. The audit trail export now includes the working-hours calendar name alongside each transition, so a CSV opened three months later still says which calendar produced the number. Fixes: status groups with a single status no longer round to the nearest minute in the Trend report.
Payment model: Paid via Atlassian
License type: Atlassian Closed-Source