Commit Graph
6 Commits
Author SHA1 Message Date
Claude 626db60658 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
2026-10-29 00:13:21 -04:00
Jens Kraemer 033e1739d2 'Start/Stop tracking' on issues#show 2021-10-05 11:26:51 +08:00
jan-imrich 9802307e5e fix rounding problem
Fixes the rounding problem. Since entry.hours is an getter with integrated round(2), its result should not be used for spent time calculation. Given the update function is called quite often (every 1-2 minutes), especially when the redmine issue is open in browser, it can disrupt the resulting overall logged time by up to 50%.
2020-12-19 08:44:15 +08:00
Jens Kraemer 30bcd5ff8c show currently running timer in window title, menu item 2020-04-25 17:09:38 +08:00
Jens Kraemer 20ccbba2c1 works, basically 2020-04-24 17:20:18 +08:00
Jens Kraemer 70257cdee0 initial commit 2020-04-22 18:03:56 +08:00