Hi! I've been using the plugin for my own time tracking and ended up extending it with a few features I personally needed. I realize not all of them may be useful to everyone, so I'm filing this issue first to check which of these you'd be interested in upstreaming before I open a PR.
- Timer pause / break tracking — a Pause/Resume button, command, and ⏸ status bar indicator. Paused time accumulates as break time, is excluded from billable hours, and survives an Obsidian restart. The daily log table gets a new
Break column.
- Calendar-month statistics — a Statistics section in the panel with month navigation, a total row, and a per-project breakdown (work, breaks, billable, session count), computed directly from the daily log tables. The current five-column format stays supported when reading history.
- Russian localization — full UI translation (panel, dialogs, commands, settings, notices), following Obsidian's language setting via the official
getLanguage() API. The file format stays English-only so parsing is locale-independent.
- Year/month folder structure — daily logs move from a flat
Daily/ folder to Daily/YYYY/MM/YYYY-MM-DD.md, with legacy flat files still readable and migrated automatically (links preserved) on the next session for that day.
- Last-used project pre-selection — the project field and the "Start timer" command pre-select the most recently used project, so plain Enter restarts it.
Since the changes share the same data model and file format, I'd prefer to submit everything as a single PR — ideally as one commit, but I can split it into separate commits per feature if that makes review easier. And if some of these don't fit the plugin's direction, I'm happy to leave them out.
Would you be open to a PR along these lines?

Hi! I've been using the plugin for my own time tracking and ended up extending it with a few features I personally needed. I realize not all of them may be useful to everyone, so I'm filing this issue first to check which of these you'd be interested in upstreaming before I open a PR.
Breakcolumn.getLanguage()API. The file format stays English-only so parsing is locale-independent.Daily/folder toDaily/YYYY/MM/YYYY-MM-DD.md, with legacy flat files still readable and migrated automatically (links preserved) on the next session for that day.Since the changes share the same data model and file format, I'd prefer to submit everything as a single PR — ideally as one commit, but I can split it into separate commits per feature if that makes review easier. And if some of these don't fit the plugin's direction, I'm happy to leave them out.
Would you be open to a PR along these lines?