<aside>
📏
CyclePulse measures durations on your work calendar. In 24/7 mode every hour counts; in Work hours mode only your configured working days and hours count. Re-visits to the same status are summed either way.
</aside>
Calendar modes
Set the mode in Work Calendar in the top bar. It applies to the table, the summary cards and every export.
- 24/7 — continuous calendar time. A day off counts the same as a working day. Best for real elapsed time and support responsiveness.
- Work hours — only your configured working days, hours, timezone and holidays count. Best for team capacity, SLA on business hours and effort estimation.
Durations are always clipped to the calendar, then summed per status. Weekends, out-of-hours time and holidays contribute zero in Work hours mode.
Timezone
Each calendar carries an IANA timezone (e.g. Europe/Kyiv). Working-hour boundaries are evaluated in that timezone, and daylight-saving changes are handled automatically — no fixed UTC offsets. Switching timezone can change a working-hours total, because the same changelog clips differently per zone.
Time in Status (per status column)
- Calculated from the issue changelog, sorted chronologically from Created to Resolution or Now
- Example: To Do 2d 4h + In Progress 1d + In Review 3h + back to In Progress 5h = In Progress total 1d 5h
- Issues that never changed status show all time in their current status (Created to Resolved or Now)
- Open issues are measured up to the moment you ran the report
Lead Time
- Created to Resolved (or to Now if still open)
- Answers: How long from request to delivery?
Cycle Time
- First time work started (first status change away from creation status) to Resolved (or Now)
- If the issue never left its initial status, Cycle Time is 0
- Answers: How long was this actively worked on?