Your TopTracker time, already in Jira.
macOS 12+ · 241 KB native binary · no Electron, no bundled browser
Your time, followed locally.
Tracking · 0:41:18
DEMO-42 · Checkout regression sweep
| Started (local time) | Jira issue | TopTracker description | Interval duration |
|---|---|---|---|
| Mar 4, 13:45:02 | DEMO-42 | DEMO-42 Checkout regression sweep | 0:41:18 |
| Mar 4, 11:02:19 | Unassigned | Sprint planning | 1:04:00 |
| Mar 4, 09:31:40 | OTHER-7 | OTHER-7 Migration follow-up | 1:22:07 |
Durations are source timestamp intervals. The live timer is an estimate; Jira totals need reconciliation.
Why this exists
Neither tool was my choice. Both were my problem.
TopTracker for time. Jira for the work. Nobody was going to merge them for me.
So every Friday: open the activity log, select the rows, paste them into a spreadsheet. A day arrives as dozens of fragments — some of them four seconds long — and none of them add themselves up. Then Jira, issue by issue, retyping the totals.
The hours I forgot to log were simply gone. Guessed at. Rounded. Written off.
TopTracker had recorded all of it. The data existed — it just never made it into Jira. So I built the part in between.
Konstantin Zotov · Spain
Capture is automatic. Posting is not.
DEMO-42 Checkout sweep maps to DEMO-42. A Jira URL works too. Anything without a key stays Unassigned — it is never guessed at. Jira · Review worklogs
A preview you can argue with before Jira sees it.
Every field in the preview is editable. Existing Jira time sits beside your sessions for context and is never subtracted for you.
| Post | Issue | Seconds | Started / timezone | Comment | Your day total | Comparison |
|---|---|---|---|---|---|---|
| DEMO-42 | 2478 | 13:45 +01:00 | Checkout regression sweep | 0 | New — no worklog of yours today | |
| OTHER-7 | 4927 | 09:31 +01:00 | Migration follow-up | 1800 | You already logged 30m — check before posting | |
| Unassigned | 3840 | 11:02 +01:00 | Sprint planning | — | No issue key — not eligible to post |
Under one minute
Sessions shorter than 60 seconds never reach the review list.
Only your worklogs
Comparison looks at entries under your own Jira account, nobody else's.
Five-minute freshness
A preview older than five minutes must be compared again before it can post.
Grouped by local day
Entries group by session start date in this Mac's timezone. Split overnight work yourself.
Local session history. Clear connections to Jira.
- TopTracker's application.log
- TopTracker.db — read-only, WAL included
- TopTracker authentication tokens
- TopTracker settings
- Screenshots
- Keyboard and mouse counters
~/Library/Application Support/TopTrack. Jira credentials go to the macOS Keychain, never to a file the app writes. What it does not do yet.
Durations are estimates
Displayed time is the interval between source timestamps, not an authoritative billed total.
No built-in mappings
No company, project or activity-to-issue rules ship with the app. Descriptions carry the key, or the session stays unassigned.
Jira needs a setup step
Connecting requires a registered Atlassian integration and an authorization service — the hosted default, or your own HTTPS origin.
It cannot track while quit
No tracking while the app is quit or the Mac is asleep. Launch at login is not implemented yet.
A missing stop is not a running timer
Starts recovered after a crash or a log rotation are labelled last-reported, never assumed live.
Tied to TopTracker's shape
Log and schema strings were read on TopTracker 1.7.8. An upgrade there may need an update here.
Stop retyping your week into Jira.
Install it, open the review window on Friday, tick the day, confirm. That is the whole routine.
The app is not signed or notarized for public distribution yet, so there is nothing to download. This page will offer the build as soon as a verified release is published.