mirror of
https://github.com/rickbarrette/stopwatch.git
synced 2026-11-17 19:50:36 -05:00
Timer safety: length limit, server-side saving, stop on close
- Maximum timer length setting (default 10h): a timer that runs past it is stopped at the limit and its entry's comment is flagged, so a forgotten timer can't add a night or weekend of hours - StopwatchTimerTickJob saves a running timer's time every minute on the server (no browser needed) and stops it at the limit on time; open tabs keep saving too - Timer updates lock the user's preference row and re-read the timer, so simultaneous saves (several tabs, the job) never add time twice - Closing an issue stops timers running on it before anything else (e.g. billing) uses its time; deleting a time entry only stops the timer running on that entry - Issue timers require a visible issue; starting again moves the timer instead of raising "timer is already running" - Tests updated and extended (limit, locking, tick job, close, delete, visibility, issue context menu); CI runs on Redmine 7.0 - Upstream's German notes translated Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01BiwYMjhoQvL7XsKKfRz4pM
This commit is contained in:
15 files changed
+366
-36
No files matched your search
@@ -28,6 +28,17 @@ Rick Barrette (2026):
|
||||
- **Colour-coded Start/Stop:** an optional setting ("Color-code Start/Stop") shows the issue Start
|
||||
link in green and Stop in red, with tinted buttons on mobile (March 2026; colours adjusted for
|
||||
readable contrast in October 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.
|
||||
- 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.
|
||||
- Closing an issue stops any timer running on it first, so the logged time is final (e.g. before
|
||||
billing). Deleting a time entry only stops the timer if it runs on that entry.
|
||||
- Issue timers require an issue the user can see; starting twice moves the timer instead of
|
||||
erroring.
|
||||
- Tests run against Redmine 7.0.
|
||||
|
||||
## Installation
|
||||
|
||||
|
||||
Reference in new issue
Block a user