show tracked time precisely including seconds
Luděk
I tracked some special activity - I need to see the exact time. Currently the time is only in minutes. I want to see seconds as well.
Log In
Brendan W
Merged in a post:
Allow time track to be precise
Ramón Jiménez
This week, ClickUp’s time tracking feature started rounding manually-entered Start and End times to the nearest 15-minute interval (00, 15, 30, 45).
Previously, users could enter any exact start/end time (e.g., 09:07–09:27) without the system modifying it.
Right now, when entering time using Start and End fields, the values are automatically rounded to the nearest 15 minutes. This makes it impossible to accurately log time when work doesn’t align with 15-minute blocks.
Users should be able to enter precise Start and End times (minute-level accuracy), without automatic rounding, which was actually something that was working OK until now.
Interestingly, if a user logs time using the duration field (e.g., “20 minutes”), ClickUp allows full precision. So the rounding only affects manual Start/End entry, which feels inconsistent.
Please revert this change and restore minute-level precision for Start/End time entries in time tracking.
C
Chi Song
Agreed, please revert this change. This makes the time tracker unusable for use cases that require precise time tracking.
Oliver Bordt
Doesn't feel good at all! I need exact times and I don't want ClickUp to round them here.
F
Frank Bar
Is it a new normal? I just reported it as a glitch. The Clickup Time Tracking menu still says after the update:
"Enter time (ex: 3h 20min) or start timer)"
So based on that I don't think forced rounding up to 15 min is intended. It seems to be a bug
Ramón Jiménez
Frank Bar I thought it was a glitch too, but ClickUp Assistant Bot replied as if it was a desired behavior and not a bug.
It is true you still can enter 3h20 min and it works OK. But you cannot enter from 09.05 up to 12.25, which is also 3h20min, because it will become 09.00 up to 12.30 (or whichever rounding ClickUp applies there). So, even if it is an intended change, I feel like it is inconsistent and a downgrade from the previous system. I am not sure what motivated the change, but should be reverted from my point of view, I don't think it benefits any use case at all.