# Planim Time

> Native desktop time tracker for Jira. Calendar view, two-way worklog sync, JQL filters, offline-first. Free tier with full tracking and manual push; Pro $10/mo unlocks automatic push, calendar, automations, idle detection, reports, and team worklog visibility; Team is bulk-priced Pro at $8/seat/mo (minimum 2 seats) for whole-workspace billing; Lifetime is a one-time $150 for Pro forever. 14-day Pro trial.

## Products

- [Planim Time for Jira](https://time.planim.app/jira): Native menu bar Jira time tracker for Mac, Windows, Linux. One-click timer, two-way worklog sync, idle detection, offline support. Tempo alternative.

## Downloads (Jira)

- [macOS (Apple Silicon)](https://cdn.planim.app/time-jira/downloads/Planim-Time-Tracker-latest-macOS-arm64.dmg)
- [Windows](https://cdn.planim.app/time-jira/downloads/Planim-Time-Tracker-latest-Windows-x64-setup.exe)
- [Linux (AppImage)](https://cdn.planim.app/time-jira/downloads/Planim-Time-Tracker-latest-Linux-x64.AppImage)
- [Linux (.deb)](https://cdn.planim.app/time-jira/downloads/Planim-Time-Tracker-latest-Linux-x64.deb)

## Pricing

- Free ($0/month): Core Jira time tracking free forever: timer, worklog editing, two-way sync, and one-click Push All to Jira.
- Pro ($10/month, $8/month billed annually): Adds automatic push on timer stop, calendar view, automations and reminders, idle detection, reports and CSV export, team worklog visibility, and per-member search. 14-day free trial, no credit card required.
- Team ($8/seat/month, $7/seat/month billed annually): Bulk-priced Pro for an entire Jira workspace: every paid seat gets full Pro features, billed per seat (minimum 2 seats), cheaper than buying Pro per person. Team stats include every member who logged time to the workspace's Jira issues, not only the paid seats. Add or remove seats anytime. 14-day free trial.
- Lifetime ($150 one-time): Everything in Pro, plus every future update, forever. One payment of $150, no subscription.

## Comparisons (Jira)

- [Planim Time vs Clockify](https://time.planim.app/jira/vs/clockify): Both tools offer two-way Jira worklogs. Planim Time is a no-admin, offline-first desktop tracker focused on Jira; Clockify is an admin-installed Marketplace app plus a general-purpose cloud timesheet, free for up to five users.
- [Planim Time vs Clockwork](https://time.planim.app/jira/vs/clockwork): Clockwork is a Jira-native plugin that adds a timesheet UI inside Jira itself. Planim Time is a native desktop tracker that pushes worklogs to Jira from the menu bar. Same hours land on the same issue; the surface around them is the difference.
- [Planim Time vs Everhour](https://time.planim.app/jira/vs/everhour): Planim Time is built around the timer, the engineer's question of 'did this hour land on the right Jira issue'. Everhour is built around the invoice, the project manager's question of 'how much did this project cost the client'. Both can track Jira; they optimise for opposite ends of the workflow.
- [Planim Time vs Hubstaff](https://time.planim.app/jira/vs/hubstaff): Hubstaff is a manager's purchase: screenshots, activity scoring, app and URL capture, optional GPS, built-in payroll. Planim Time is the engineer's: a menu-bar timer that writes Jira worklogs and captures nothing else. Different buyers, different tools.
- [Planim Time vs Tempo Timesheets](https://time.planim.app/jira/vs/tempo): Planim Time is a native desktop tracker built for engineers; Tempo Timesheets is a Jira-embedded plugin built for approvals and finance-oriented reporting, with separate Tempo products for capacity and financial management. They overlap on 'log time to Jira' and diverge above it.
- [Planim Time vs Toggl Track](https://time.planim.app/jira/vs/toggl): Toggl Track pulls Jira issues into a Toggl timesheet. Planim Time pushes your hours out as Jira worklogs. The integrations point in opposite directions, and that single decision shapes everything else.

## Blog

- [Jira timer vs calendar vs weekly timesheet: when the number gets written](https://time.planim.app/blog/jira-calendar-vs-timesheet) (2026-08-04): Live timer, calendar reconstruction, or a weekly timesheet grid for Jira time tracking: what each model does to worklog accuracy, and how to choose.
- [Jira time tracking without admin rights: what actually works](https://time.planim.app/blog/jira-time-tracking-without-admin-rights) (2026-07-23): Track time in Jira Cloud without a Marketplace install. Compare native worklogs, OAuth, and API-token tools, including the permissions each path needs.
- [Idle detection lands in our Jira time tracker: keep, subtract, or stop](https://time.planim.app/blog/jira-time-tracker-idle-detection) (2026-07-22): Planim Time 0.4 adds idle detection to our native Jira time tracker: keep, subtract, or stop the gap when you step away. Plus one-click Atlassian sign-in.
- [Jira time tracking on mobile: a phone logs time, it doesn't time it](https://time.planim.app/blog/jira-time-tracking-mobile) (2026-06-30): You can log work in the Jira mobile app, but it has no timer. Why a phone is for logging time after the fact, not for running a clock as you work.
- [Capacity planning in Jira with time tracking data](https://time.planim.app/blog/capacity-planning-jira-time-tracking) (2026-06-26): Jira measures load, not capacity. Why its workload reports total remaining estimate, and how logged hours become a number you can plan a sprint against.
- [How to change logged hours in Jira: edit, move, and delete worklogs](https://time.planim.app/blog/how-to-change-logged-hours-in-jira) (2026-06-25): Open the issue, find the entry on the Work log tab, and use its edit or delete control. That's the native path; a calendar is faster if you edit often.
- [What did I work on? Rebuilding Jira worklogs from your own activity](https://time.planim.app/blog/reconstruct-jira-worklogs-from-activity) (2026-06-24): Jira already records what you touched: assignments, comments, status changes. Here is how to turn that activity trail back into honest worklogs.
- [Logging time across multiple Jira projects and instances](https://time.planim.app/blog/time-tracking-multiple-jira-projects) (2026-06-22): Tracking time across many Jira projects works natively; across separate instances it doesn't. The line is the authorization boundary, and where JQL stops.
- [Jira automatic time tracking: what "automatic" really means](https://time.planim.app/blog/jira-automatic-time-tracking) (2026-06-10): No tool tracks Jira time fully automatically. What the word covers: activity capture, start/stop triggers, API delivery, and the step that stays manual.
- [How to export Jira worklogs to CSV or Excel: totals vs worklog rows](https://time.planim.app/blog/export-jira-worklogs-csv) (2026-06-09): Jira's CSV export rolls worklogs up to one Time Spent number per issue, and its Log Work columns carry wrong dates. Three ways to get real worklog rows.
- [Time tracking without micromanagement: a guide for Jira team leads](https://time.planim.app/blog/time-tracking-without-micromanagement) (2026-06-09): Time tracking becomes micromanagement when the data answers 'is this person working enough'. Four dials a lead controls, and a rollout that keeps trust.
- [Clockify vs Tempo for Jira: two-way sync vs finance depth](https://time.planim.app/blog/clockify-vs-tempo-jira) (2026-06-02): Clockify and Tempo both integrate inside Jira. Compare the five-user free tier, two-way worklog sync, admin install, approvals, budgets, and system-of-record trade-offs.
- [Why your Jira time estimates are always wrong (and what to do)](https://time.planim.app/blog/why-jira-estimates-are-wrong) (2026-05-31): Jira estimates are biased low, not randomly off. Why software estimates run short, why Jira hides the miss, and how logging real time calibrates them.
- [The Jira Cloud Worklog REST API: a practical guide](https://time.planim.app/blog/jira-worklog-rest-api-guide) (2026-05-29): The Jira Cloud worklog REST API end to end: authentication, add/read/edit/delete, bulk worklog/updated and worklog/list endpoints, retries, and examples.
- [Billable hours in Jira: no native field, what teams do instead](https://time.planim.app/blog/billable-hours-in-jira) (2026-05-25): Jira has no billable flag. Four patterns teams use (labels, custom fields, separate projects, add-ons) and the issue-vs-worklog tradeoff that decides.
- [Story points vs hours in Jira: can you use both?](https://time.planim.app/blog/story-points-vs-hours-jira) (2026-05-23): Story Points and hours in Jira measure different things. When to use each, where Sprint Burndown clashes, and the pattern that works when teams try both.
- [Tempo vs Clockwork: which Jira time tracker for your team](https://time.planim.app/blog/tempo-vs-clockwork) (2026-05-21): Tempo and Clockwork compared head-to-head: prices, free tiers, approvals, leave tracking, and the team size where the math flips between them.
- [Jira time tracking reports: what's built in and where it stops](https://time.planim.app/blog/jira-time-tracking-reports) (2026-05-19): What Jira's built-in time tracking reports cover, and where they stop: no cross-project totals, no date ranges, no per-user timesheet.
- [How to log work in Jira: the worklog dialog, JQL, and the API](https://time.planim.app/blog/how-to-log-work-in-jira) (2026-05-17): Logging work in Jira three ways: the worklog dialog field by field, JQL to check what you logged, and the REST API for scripted worklogs.
- [Tempo Timesheets alternatives in 2026, by use case](https://time.planim.app/blog/tempo-alternatives) (2026-05-16): Honest shortlist of Tempo alternatives organised by what your team actually needs: simpler timers, lighter PSAs, in-Jira plugins, or monitoring tools.
- [Original Estimate vs Remaining vs Time Spent in Jira](https://time.planim.app/blog/jira-original-estimate-vs-time-spent) (2026-05-15): What Original Estimate, Remaining Estimate, and Time Spent really do in Jira, how they move when you log work, and which one your sprint reports use.
- [Forgot to log time in Jira? A clean way to backfill worklogs](https://time.planim.app/blog/backfill-jira-worklogs) (2026-05-14): Forgot to log time in Jira? How to backfill worklogs for past dates using your calendar, git history, and the REST API, with honest rounding rules.
- [Tracking Jira time without screenshots or activity scores](https://time.planim.app/blog/jira-time-tracking-without-screenshots) (2026-05-13): What screenshot-heavy Jira trackers capture, the morale, legal, and security costs of it, and the case for a timer that records hours and nothing else.
- [Leaving Tempo: a working playbook for moving Jira worklogs](https://time.planim.app/blog/migrate-from-tempo-to-desktop-tracker) (2026-05-13): How to export historical worklogs from Tempo, pick a successor, backfill Jira, and the pieces of your workflow that don't survive the move.
- [Free Jira time trackers in 2026: which ones are actually free](https://time.planim.app/blog/free-jira-time-trackers) (2026-05-13): Seven Jira tracking products plus Jira's built-in worklog, and several definitions of 'free'. See which free tiers include real Jira sync and which gate it behind paid.
- [How to track time in Jira: every method, ranked by friction](https://time.planim.app/blog/how-to-track-time-in-jira) (2026-04-30): Five ways to log time in Jira, ranked by setup effort: native worklogs, Marketplace plugins, browser extensions, desktop apps, and the worklog API.
- [The best Jira time trackers for engineering teams in 2026](https://time.planim.app/blog/best-jira-time-trackers-for-engineers) (2026-04-30): Five Jira time trackers compared by an engineer who built one of them: Tempo, Clockwork, Everhour, Clockify, Planim Time, ranked by use case.
- [Where Jira time trackers store credentials: API tokens and OAuth](https://time.planim.app/blog/where-jira-time-trackers-store-your-api-token) (2026-04-29): A security review of how Tempo, Clockwork, Everhour, Clockify, and Planim Time handle Jira API tokens, OAuth credentials, Marketplace access, and revocation.
- [Two-way Jira worklog sync: how to verify it](https://time.planim.app/blog/two-way-jira-worklog-sync) (2026-04-26): What two-way Jira worklog sync means, how to test edits and conflicts, and how Planim Time reconciles Jira with its local offline store.
- [Why a desktop Jira time tracker, not a Marketplace plugin](https://time.planim.app/blog/why-native-desktop-time-trackers) (2026-04-26): Why we shipped Planim Time as a menu-bar binary, not a Jira Marketplace plugin, and how that affects outages, offline tracking, and security.

## Optional

- [Full project context](https://time.planim.app/llms-full.txt): extended features, security, and FAQ
- [Changelog](https://time.planim.app/changelog): desktop app release notes, newest first
- [Privacy Policy](https://time.planim.app/privacy)
- [Terms of Service](https://time.planim.app/terms)