Time in status used to be shown in hours only. That works for a review that takes half a day, but not for a task that sat in "Blocked" for over a year: "10956h" says little until you divide it in your head.
What changed
On Time Tracking → Workflow Bottleneck Detector, every duration (the average per status, the total waiting time, the bars and the tasks behind a status) now uses the largest unit that fits, with at most two units:
| Time in status | Shown as | |---|---| | under 1 hour | 45m | | under 1 day | 5.5h, 14h | | under 1 week | 2d 5h | | under 1 month | 2w 3d | | under 1 year | 6mo 17d | | 1 year or more | 1y 3mo |
This is calendar time: a day is 24 hours and a month is an average calendar month (30.4 days). Effort figures elsewhere on the page, such as actual and expected hours on tasks over baseline, stay in hours, because a "day" of effort would wrongly read as a working day.
What happens to your numbers
Nothing. Only the display changed. The API still reports hours, and now also returns the readable label beside each value (avg_duration, total_duration, status_duration), so the AI tools connected through the MCP connector quote the same figures you see in the app.