Easiest and precise time tracking. Never log work manually again. Overview your team or company worklogs with powerful reportsGet it now
Automatically track time when the issue is transitioned between statues or assignees. Once moved to In Progress it will start counting the time. Moving the issue to Done or To Do status category will stop the timer.
A visual overview of time spent vs estimated gives you an easy way to tell how far is the end. Plus you can see how much time each contributor worked on the issue. It works with Next-Gen projects too!
Clockwork Automated Timesheets offers automatic time tracking mode integrated with Jira workflow transitions. Time spent is calculated for every issue moved to and out of the "In progress" category.
Tracked time is stored in Jira work log so you can still log work manually and use Jira reporting tools.
Questions or feedback? Contact us through one of the following:
We explain the difference on the following documentation page: Free vs Paid subscription.
Atlassian is responsible for handling subscriptions and payments (vendors only set per-user price). It should be enough to just start the trial.
Issue Checklist and all other add-ons for Jira Cloud (as opposed to Jira Server plugins) are loaded in separate iframes inside the Jira page. This approach ensures security (iframe code cannot access the main page) but also lets the browser load the content of the add-on asynchronously without blocking the main page.
There are no limits at all. You can add as many items and templates and as often as you want
Atlassian is responsible for counting a number of users. It usually equals the number of users registered in your Jira (excluding Service Desk customers).
The on-premise version is implemented via a new Custom Field Type, while the cloud version is a Connect App. Since Atlassian does not allow third-party Custom Fields on their cloud instances, on-premise and cloud Apps have different architectures and integration points in Jira.
Their feature set is a little different, but as Atlassian improves its Connect API, both versions are becoming more and more similar. Read more about comparison here.
Checklist for Jira Server and Data Center versions have been developed as a custom field since it offers a much tighter integration into Jira.
It allows more features like viewing checklists in the Create, Edit or Transition screens or bulk updating the checklist of many issues at once.
Don’t worry; adding a Checklist custom field is fast and straightforward.
Checklist for Jira is highly configurable to meet a variety of needs as no two organizations work the same way. Use only the features you need. As your needs to grow, Checklist for Jira can grow with you.
Read this blog post we wrote.
For Cloud, we keep the data for one year as some clients repurchase Checklist for Jira. But if you want us to completely remove your data, please open a support ticket.
As for the Server and Data Center, the data stays until you delete the Checklist Custom Field.
What this means is that you need to buy the same user tier for any app that you have for the host product (example Jira).
Automatic timers are started and stopped according to the current workflow your project uses. To learn more read When do automatic timers start / stop?
Yes, Clockwork works with Tempo as well, but our plan for the future is to offer similar features that you won't be needing Tempo.
When working on a sub-task time spent is reported only on the sub-task. Parent issue is not updated so you should not keep the sub-task and the parent issue in progress at the same time.
If you want to know more about the way we calculate time please check out How time spent is calculated (with working hours)?
Time spent on the issue is logged only once the timer is stopped. It means that currently Clockwork will log all time spent at the last day. It will not spread the time through days the timer was running.