Solving the Jira Time Tracking Problem Nobody Talks About
Most development teams share a quiet frustration with time tracking: the work gets done inside Jira, but recording how long it took requires a separate action that nobody wants to take. Clockwork for Jira tackles that problem directly. Built by HeroCoders, an Atlassian Platinum Marketplace Partner headquartered in Gda?sk, Poland, Clockwork generates worklogs automatically when issues move through your Jira workflows. We score it 7.8 out of 10 in the time and attendance software category, with its strongest marks in pricing and ease of use, and its biggest limitations tied to how faithfully your team uses Jira's status transitions.
HeroCoders was founded in 2018 by Pawel Niewiadomski and Jacek Jaroczynski, and the company's team includes former Atlassian employees and contractors with a combined 50-plus years in the Atlassian ecosystem. Their products serve over 70,000 companies worldwide, with Clockwork available in three tiers: Clockwork Pro (the full-featured version), Clockwork Lite (a budget option launched in January 2025), and the legacy Clockwork Free edition, which accumulated nearly 10,000 installs before being sunset. The Pro version currently holds Cloud Fortified status, Atlassian's highest trust designation for cloud apps.
How Clockwork Tracks Time Without User Input
The core concept is simple but effective. When a Jira issue moves into an active status, like "In Progress," Clockwork starts an automatic timer tied to the assignee. When the issue transitions out of that status, the timer stops and a worklog is created. The app uses each user's configured working hours to calculate actual time spent, subtracting overnight hours, weekends, and holidays so the logged time reflects realistic work patterns rather than raw elapsed time.
This no-touch tracking approach is Clockwork's defining capability. For a scrum master managing a team of eight developers, the difference is tangible: instead of chasing people to fill in timesheets every Friday, worklogs populate themselves as the team does its normal work. One practical detail that helps accuracy is the working hours configuration. Administrators set default schedules at the organization level, but individual users can adjust their own hours through the Clockwork panel. Holiday calendars can also be configured per location, which matters for distributed teams spanning multiple countries.
Beyond automatic tracking, Clockwork Pro supports two additional methods. Users can start and stop timers manually on individual issues for tasks that need more precise measurement. They can also create manual worklogs after the fact. The Pro version allows unlimited timers, while Clockwork Lite caps them at 300 per month. One UX consideration: the "My Work" view where users manage their timers and recent worklogs defaults to a timesheet layout, but there's a toggle to switch to a calendar view. The calendar option was extended to Clockwork Lite in a March 2025 update, and it makes reviewing the week's logged time more intuitive than scrolling through rows.
Where the automatic timers lose precision is during breaks and task switches. If a developer walks away from their desk with an issue sitting in "In Progress," the timer keeps counting until working hours end or the issue transitions. Teams that multitask across several issues simultaneously will also find that Clockwork only tracks one automatic timer per user at a time, since it ties tracking to the assigned issue's active status. That's a design decision, not a bug, but it does mean the automatic approach works best for teams that move issues through workflows methodically.
Clockwork Pricing and What It Costs Per Year
The most striking thing about Clockwork's pricing is the free Pro tier. Teams of up to 10 users get full access to Clockwork Pro at no cost. HeroCoders extended this in 2024, making it one of the few full-featured Jira time tracking plugins with a fully functional free plan rather than a stripped-down trial.
For paid tiers, Clockwork Pro runs approximately $2.50 per user per month through the Atlassian Marketplace, though the exact rate follows Atlassian's tiered pricing model where per-user costs decrease as team size grows. For a team of 25 users, that works out to roughly $750 per year. A team of 50 would pay approximately $1,500 annually. Those figures sit well below most alternatives in the Jira time tracking space. Clockwork Lite offers an even lower entry point for teams that don't need cost tracking, advanced reporting, or unlimited timers. A 30-day free trial is available for both Pro and Lite if you want to test before committing.
The cost and rate tracking feature, introduced in beta during 2024, adds a financial layer on top of the time data. Administrators assign hourly costs and billable rates per user, and Clockwork calculates project labor costs and revenue projections from logged worklogs. The rates are currently universal per user and don't vary by project, which limits flexibility for agencies or consulting firms billing different clients at different rates. HeroCoders has indicated that variable rates by project and time period are on the development roadmap.
Timesheet Reports and Jira Integration Depth
Clockwork's reporting starts with timesheet views that can be filtered and broken down by virtually any Jira field: projects, epics, labels, teams, custom fields, and worklog attributes like billable versus non-billable. The multi-level breakdown is where the reporting earns its keep. You can, for instance, view total hours by project, then drill into individual epics, then see per-user time within each epic. If you manage KPIs tied to logged hours, this layered view should give you what you need without exporting to a separate analytics tool. The estimates-versus-actuals comparison adds another practical layer. If your team uses Jira's original estimate field, Clockwork can display tracked time against those estimates at the issue, epic, and project level, which makes this data immediately useful for sprint retrospectives or project post-mortems. For billing-focused teams, the ability to filter by billable attribute and lock completed billing periods prevents retroactive edits from distorting invoiced figures.
Integration with Jira goes deeper than most Jira time tracking plugins. Clockwork data syncs with Jira's native worklogs, which means you can use JQL to find issues with running timers, display accumulated hours on Kanban and Scrum board cards, and show time tracking data in the Jira Service Management portal. There's also a workflow validator that prevents issues from transitioning unless time has been logged, which is a handy enforcement mechanism for teams where timesheet compliance is a recurring problem. Dashboard gadgets were added in 2024, giving managers a persistent view of team time data without navigating to the Clockwork interface.
One observation on the reporting interface: the filter controls across the top of the timesheet view pack in a lot of options, and finding the right combination of breakdowns takes a few tries if you're new to the tool. The filter layout isn't labeled as clearly as it could be, particularly the distinction between "Group by" and "Break down by," which serve overlapping but distinct purposes. Once you've built a few saved views, though, day-to-day use becomes quick.
Is Clockwork the Right Fit for Your Team?
Clockwork's sweet spot is a Jira-native development team where the workflow is the source of truth. Picture a software consultancy with 15 developers working across three client projects. Each developer picks up issues from the backlog, moves them through a standard workflow of "To Do," "In Progress," "In Review," and "Done." In this environment, Clockwork's automatic tracking captures billable hours without any developer ever opening a timesheet. The billing administrator pulls reports at month-end, filters by project and billable attribute, and has the data needed to invoice clients.
The fit weakens in environments where Jira isn't the primary work hub. If your team splits time between Jira issues and work that happens outside Jira, like client calls, internal meetings, or tasks tracked in other tools, Clockwork can only capture the Jira portion. Google and Outlook calendar integration in the Pro version helps bridge the gap for scheduled meetings, letting users log time from calendar events. But unstructured work that doesn't map to a Jira issue or a calendar event falls through the cracks.
Teams with inconsistent workflow discipline will also struggle. If developers routinely leave issues in "In Progress" overnight or over weekends without transitioning them, the working hours calculation handles most of that. But issues left in active status for days while other work takes priority will generate inflated worklogs that need manual correction.
Where Clockwork Stops
Within the time and attendance category, the most visible gap is approval workflows. Clockwork doesn't include a native timesheet approval process where managers review and sign off on submitted hours before they're finalized. Teams that need a formal approval chain will need to manage that step outside the tool or through Jira automation rules.
The reporting, while functional, lacks some advanced capabilities that larger organizations may expect. There's no built-in resource capacity planning, no forecasting based on historical time data, and no visual burndown-style reports for time budgets. The Excel export covers most ad hoc analysis needs, but teams with complex project accounting requirements may find themselves building reports outside the app.
Mobile access follows Jira's mobile app rather than offering a standalone Clockwork mobile experience. You can view and create worklogs from Jira Mobile, but the full Clockwork reporting and configuration interface is a desktop experience.
Our Verdict on Clockwork for Jira
Clockwork earns its 7.8 by solving one specific problem well: it removes the manual effort of time tracking for teams that already run their work through Jira. The automatic tracking engine is a genuine differentiator, and the free Pro tier for small teams makes it an easy first choice for organizations just starting to track time. At $2.50 per user per month, even the paid tiers represent strong value relative to the category.
The limitations are real but predictable. If your team doesn't transition Jira issues consistently, the automatic data won't be reliable. If you need approval workflows, resource planning, or reporting that goes beyond timesheet breakdowns, you'll hit the ceiling. And if significant portions of your team's work happen outside Jira, Clockwork can only capture part of the picture. For Jira-centric teams with clean workflows, though, this is one of the few time tracking tools where end users genuinely don't have to change their behavior to produce accurate timesheets.