Dwellwise documentation (source for the public knowledge base)
Get started (5 minutes)
- Calendars. Jira settings > Apps > Dwellwise > Calendars. Edit the default calendar (it
starts as Mon-Fri 09:00-17:00 UTC) and add one per office or team: time zone, working
periods per day (split shifts like
08:00-12:00, 13:00-17:00), holidays. - People and projects. Give people their calendar. People without one count on the default calendar's hours in their Atlassian profile time zone (when they share it; you can turn this off under Settings). Unassigned time counts on the project's calendar, then the default calendar.
- Run a report. Apps > Dwellwise (or Dwellwise in a project's sidebar). Enter any JQL, keep "Whoever held it", and Run report.
- Add fields (optional). Jira settings > Work items > Fields > Create field > Dwellwise time in status (a number) or Dwellwise status check (On track, At risk, Breached). Open the field's context and Configure it. Then Jira settings > Apps > Dwellwise > Fields > Recalculate to fill in existing work items.
How working time is counted
An item's history is split into stretches with the same status and the same assignee. Each stretch counts the working hours of one calendar:
- Whoever held it (handoff-aware): the assignee's own calendar; else the default calendar's hours in the assignee's profile time zone; else the project's calendar; else the default calendar. Unassigned stretches use the project's calendar.
- A named calendar: that calendar for every stretch.
- 24/7: clock time.
Holidays are dates in the calendar's own time zone. Daylight saving changes are handled by the time zone. "Working days" units divide by the calendar's average working day (8 hours for 09:00-17:00); for handoff mode, the default calendar's day.
The Time in status panel on each work item shows every stretch: status, holder, calendar, working time and clock time. Switch its calendar to compare.
Cycle time and lead time
- Cycle time starts at the first entry into a start status (default: any status in the In Progress category) and stops at the last entry into a stop status (default: any Done category status), counted only if the item is in a stop status now. A reopened item is running again.
- Lead time runs from creation to the same stop.
- Choose your own start and stop statuses in the report, or per field context.
Reports
- Cards: items, finished items, cycle and lead time medians and 85th percentiles, items over a threshold.
- Overview: working time per status (median and 85th percentile; Done-category statuses are left out of the chart), cycle time by week finished, a status table with mean, median, 85th and 95th percentiles.
- By group: assignee, work type, project or current status.
- Who held the work: working time per person and status, on each person's own calendar.
- Items: every item, sortable, with per-status times; the CSV has every row (working hours or working days; the detailed CSV adds clock hours and visits per status).
- Reports run with your Jira permissions and are kept for your admin's retention (default 7 days) under "Your recent reports". Big reports keep running if you close the tab.
Fields
| Measure | Value |
|---|---|
| Time in the current status | Working time since the item entered its current status |
| Total time in chosen statuses | Working time across every visit to those statuses |
| Cycle time | Running until the item stops, then final |
| Lead time | Running until the item stops, then final |
Units: working hours, working days, minutes or calendar days. Thresholds: "At risk from" and "Breached from" in the field's unit; a status check field shows On track, At risk or Breached.
Values update when the status, assignee, project or work type changes, when someone opens the
item, and on the background clock for open items (every 1, 3, 6 or 24 hours; Settings).
Example JQL: "Review time" > 16, "Review SLA" ~ "Breached" AND statusCategory != Done,
project = WEB ORDER BY "Cycle time" DESC.
Fields can't trigger Automation rules (a Forge platform limit) and don't add entries to the History tab.
Dashboard widget
"Cycle time and time in status (Dwellwise)" works on the new Jira dashboards (and classic ones): a cycle time trend (median and 85th percentile per week for items finished in the last N weeks) or working time per status with an optional threshold line. It reads up to the 500 most recent matching items and refreshes every 10 minutes.
Classic Jira dashboards and their gadgets stop working on 17 May 2027, when Atlassian retires them. Before then, add the widget to a new Jira dashboard and pick the same settings.
Admin settings
Who can run reports (groups; Jira admins always can), report size limit, how long results are kept, background refresh interval and size, and whether profile time zones are used.
Limits
One report: up to 250,000 work items (default limit 50,000). Background refresh: up to 100,000 open items per run (default 20,000). Changes with unreadable dates in imported history are skipped and counted.