Add a closing time that stops timers

A new Closing time setting (e.g. 17:00, in each user's time zone): a timer started before closing stops
at closing time and its entry's comment notes it, so no time is logged after closing, even when nobody
stops it until the next day. A timer started after closing is overtime and keeps running, up to the
maximum timer length.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01BiwYMjhoQvL7XsKKfRz4pM
This commit is contained in:
Claude committed 2026-10-31 08:41:57 -04:00
1 parent 7266f7842a
commit 7349d9cf5a
6 files changed
+108 -4

No files matched your search

+3
View File
@@ -31,6 +31,9 @@ Rick Barrette (2026):
- **Timer safety (October 2026):**
- *Maximum timer length* setting (default 10 hours): a forgotten timer is stopped at the limit and
its time entry's comment is flagged, instead of adding a night or weekend of hours.
- *Closing time* setting (e.g. 17:00, in each user's time zone): a timer started before closing
stops at closing time, so no time is logged after it, and the entry's comment says so. A timer
started after closing is overtime and keeps running, up to the maximum timer length. Blank for none.
- Running timers are saved every minute on the server (a background job), so issues show the time
live even with no browser open; open tabs keep saving too. Saves lock the timer, so several tabs
can't add the same time twice.