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
- New top-menu page listing running timers: owner, issue, project,
activity, start time, time on this run and entry total, oldest first;
refreshes every minute
- Role permissions "View running timers" and "Stop other users' timers",
checked against each timer's project; users can always stop their own
- A timer can be stopped at an earlier time (when the person left):
hours logged after it are taken off the entry, and the comment notes
who stopped it and when
- Timers now record when they were started (session_started_at); timers
running from before show "unknown" until restarted
- Integration tests for permissions, project scoping and stopping; unit
tests for Timer#stop_for
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01BiwYMjhoQvL7XsKKfRz4pM
- 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
- Colour-coded Start/Stop links use #2e7d32 / #c62828, which meet the
4.5:1 text contrast ratio on white and on the mobile backgrounds
(limegreen was ~2:1, red ~4:1)
- Selectors match the end of the link address (/timer/start,
/timer/stop), exactly what stopwatch.js rewrites, instead of any
address containing "start"/"stop"
- highlighted_links setting uses a string key like default_activity,
has a default, and the form sends 0 when unticked
- Context-menu hook uses the calling view (hook_caller) instead of
building a new view context
- README: "Changes in this fork" section (GPLv3 modification notice)
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01BiwYMjhoQvL7XsKKfRz4pM