Clockwork for Jira (Lite)

Master Timesheets with a Simple Jira Time Tracker

Take command of time tracking in Jira. Capture time accurately, gain valuable insights, and conquer deadlines with this simple, low-cost time tracking solution.

550K+

users

10,000

installs

1.9M

timers (2023)

63.1M

timesheets (2023)

Other Features

Set Working Hours

Define your working hours within Clockwork to ensure accurate time tracking.

Multiple Timers

Allow multiple team members to track their time on a single issue simultaneously.

Customisable Exports

Exportable timesheets with simple, intuitive UI. Select your preferred fields for data export.

Ready to Get Started?

Try the power of Clockwork for Jira (Lite) today and always! Or, unleash its full power with the Pro version for unlimited timers, advanced automation features, and more.

Frequently Asked Questions

Clockwork Pro includes additional features for tracking time and for viewing tracked time. It also includes cost and rates tracking. See this page for a detailed comparison.

Clockwork Lite uses the issue status and the assignee’s configured working hours to calculate the amount of time worked. See the documentation for examples.

Automatic timers are started and stopped according to the issue status, and the assignee’s configured working hours. See the documentation for more information:
Automatic Timers
When Do Automatic Timers Start and Stop

Time is logged into Jira when a worklog is created. If you are using timers or automatic time tracking, the worklog will be created when the timer is stopped. Clockwork Lite divides total time spent over the number of days the timer was running in accordance with the users configured working hours. So, for a timer that ran for multiple days, on the last day, Clockwork Lite will create a worklog entry for each day the timer ran.

In Clockwork Lite, time spent is shown only on the issue where it was logged. Parent issues are not updated with time logged on sub-tasks. Therefore, if you are using automatic time tracking you should not have the parent issue and any of its subtasks in an active status at the same time.

Explore Powerful Resources

Productivity Tips and Tricks
Explore More
Explore More
Professional Services and Support
Find Solution Partners
Find Solution Partners