The Jira time tracker
that doesn't touch your account
For developers, support engineers, project managers and consultants who bill against Jira tickets. Auto-detects ticket keys (PROJ-1234) and project codes from your active browser tab. Windows + macOS, hours stay on your machine.
14-day free trial. No account or credit card. Windows 10/11 (64-bit); macOS 13+ on Apple Silicon (alpha).
How it works with Jira: a desktop app that reads the active browser tab title on your machine and pulls out the ticket key.
Works on Jira Cloud, Server and Data Center. Zero footprint inside Atlassian - no app installed in your instance, no API token, no OAuth flow, nothing for your admin to approve. Time entries stay as plain JSON on your laptop, ready to export to Excel / CSV / branded PDF invoice. Worklog write-back into Jira is on the roadmap as an optional paid Connect add-on.
How auto-detection works on a Jira tab
Window-title parsing, no API token.
Read the active tab title
On a Jira ticket the tab title is "PROJ-1234 Add login button - Jira" (Cloud / Server / Data Center all use this format). The app reads this on your machine.
Parse out the ticket key + summary
The Standalone edition extracts "PROJ-1234" as the case identifier and "Add login button" as the description. The project code "PROJ" becomes the customer / project bucket.
Pre-fill, you click Start
The customer field is filled with the project code, the case field with the ticket key + summary. Click Start. Optional auto-start fires the timer once the tab has been focused for the configured number of seconds.
What this app does and does not do for Jira
Local ticket-key parsing
Read the browser tab title on your desktop, extract the Jira ticket key, pre-fill the case field. Works for Cloud, Server, Data Center and Service Management.
Local timesheet + invoicing
JSON files on your machine, Excel / CSV / PDF invoice export. Multi-device sync via Dropbox / OneDrive / iCloud / SyncThing folder you already have.
Group by project automatically
The project prefix (PROJ-, OPS-, SUPP-) becomes a customer/project bucket. Time totals roll up per project automatically.
Authenticate to Atlassian
No OAuth flow, no API token, no Atlassian Cloud login, no service account. The app does not know your Jira credentials and cannot use them.
Call the Jira REST API
Zero outbound calls to *.atlassian.net or any Atlassian-owned endpoint from this app. Your IT department's egress logs will confirm this.
Post worklogs back to Jira
No automatic worklog creation in the current version. Export to CSV and paste manually, or wait for the optional Connect add-on.
How this compares to inside-Jira time trackers
Different shape, different job.
| Need | Workforce Time Tracker | Inside-Jira time-tracking apps |
|---|---|---|
| Installed inside Jira | No | Yes (Atlassian app) |
| Atlassian admin approval needed | No | Yes |
| Auto-detect ticket key from tab | Yes | Yes (inside Jira) |
| Works when Jira is offline / VPN down | Yes | No |
| Hours stored on your machine | Yes | In Atlassian Cloud / Jira DB |
| Worklogs land in Jira automatically | No (export-only today) | Yes |
| PDF invoice generation | Yes | Add-on or external |
| Multi-device sync via your folder | Yes (Dropbox / OneDrive / iCloud / SyncThing) | Cloud-only |
| Cost for 5 users / year | ~EUR 250 | ~EUR 600 - 1500 |
EUR 50/user/year on annual billing. Inside-Jira app cost based on typical per-user-per-month tiers for Atlassian Marketplace time-tracking apps as of May 2026.
Common Jira time-tracking questions
Does this connect to my Jira account?
No. The app reads the title of your active browser tab and parses out the Jira ticket key. It does not authenticate to Atlassian, does not store an API token, and does not call the Jira REST API. There is no app inside Jira to install.
Does it post worklogs back into Jira tickets?
Not in the current version. Time entries stay in local JSON files. You can export to Excel / CSV and bulk-paste worklog data into Jira yourself, or wait for the optional paid Connect add-on which is on the roadmap.
Will it work with Jira Cloud, Jira Server and Jira Data Center?
Yes. All three render the ticket key in the browser tab title (e.g. PROJ-1234 Add login button - Jira). The window-title parser handles all three the same way.
Does it work with Jira Service Management?
Yes. Service Management tickets follow the same key-prefix-and-number format (e.g. SUPP-789 Customer cannot log in). The parser detects them as part of the Standalone edition.
How does this compare to inside-Jira time trackers?
Different shape. Inside-Jira trackers live in your Atlassian instance and write back into Jira reports. This product is the desktop-side companion: it reads the Jira ticket key from your active browser tab (Cloud, Server or Data Center) and stores your time entries as plain JSON files on your own machine, ready to export to Excel / CSV / branded PDF invoice. Nothing is installed inside Jira, no API token is needed, and your time data never goes near Atlassian's cloud.
Can I track multiple Jira projects at once?
Yes. The app records each ticket as its own time entry, automatically grouped by project key (the prefix before the dash). Switching tabs between PROJ-1 and OPS-77 will be detected as switching customer/case automatically.
Try it for 14 days, no account, no credit card
Same product on Windows and macOS. One licence covers both.
Download the trial