Clockwork Automated Timesheets - Free

Clockwork Automated Timesheets - Free

Easiest and precise time tracking. Never log work manually again. Overview your team or company worklogs with powerful reports

Get it now
Hosting

Cloud

Compatible with
Jira Software IconJira Align IconJira Service Management IconJira Work Management Icon
Jira Software
Jira Align
Jira Service Desk
Jira Work Management
Pricing

Free!

Free!

See details
Initial Release

September 1, 2018

Active Instances
+

4500

Clockwork Automated Timesheets - Free
No brainer time tracking

No brainer time tracking

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.

Issue progress

Issue progress

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!

Reports

Reports

Every project gets its own report so you can see how much time spent was reported in total or by each member of the team separately. You can also group the data in various ways and export to Excel.

More Details

Try it free

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.

It is a free version of Clockwork Pro. It comes with some limitations.

Key features:
  • automatically starts/stops a timer during issue transition
  • a user can manually start/stop a timer as well
  • you can decide to use automatic or manual timers (or both)
  • supports multiple timers per issue for every contributor
  • holiday calendar support - will not track time for holidays, etc.
  • timesheet report
  • export to Excel
  • your own automated reports via Clockwork API
  • see what's missing in Free version compared to Pro

Questions or feedback? Contact us through one of the following:

Frequently Asked Questions

What is the difference between Pro & Free ?

down arrow icon

We explain the difference on the following documentation page: Free vs Paid subscription.

How can I buy Issue Checklist Pro?

down arrow icon

Atlassian is responsible for handling subscriptions and payments (vendors only set per-user price). It should be enough to just start the trial.

Where can I find Privacy Policy, Security Statement and Terms of Use documents?

down arrow icon

Lorem ipsum dolor sit amet, consecteturor adipiscing elit. Tincidunt donec vulputate ipsum erat urna auctor. Eget erliorer phasellus ideirs. Lorem ipsum dolor sit amet, consecteturor adipiscing elit. Tincidunt donec vulputate ipsum erat urna unash.

Can the Issue Checklist slow down my Jira?

down arrow icon

No.

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.

Are there any limits on the paid version?

down arrow icon

There are no limits at all. You can add as many items and templates and as often as you want

How much (and for how many users) will I pay for Issue Checklist Pro?

down arrow icon

Atlassian is responsible for counting a number of users. It usually equals the number of users registered in your Jira (excluding Service Desk customers).

Frequently Asked Questions

Are the Cloud and on-premise (Server and Data Center) versions identical?

down arrow icon

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.

Why do I need to first create a custom field in the Server and Data Center versions?

down arrow icon

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.

What if I don’t need all the checklist features?

down arrow icon

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.

How can I best implement Definition of Done (DoD) and Acceptance Criteria (AC) in Jira?

down arrow icon

Will I lose my data if I uninstall the app or my trial ends?

down arrow icon

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.

I like Checklist for Jira, but can I buy it only for a subset of users?

down arrow icon

Unfortunately, Atlassian does not allow this and we are required to follow Atlassian licensing rules. All Atlassian Marketplace apps must match (or exceed) the parent product in terms of user tier.

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).

Frequently Asked Questions

When are automatic timers started / stopped?

down arrow icon

Automatic timers are started and stopped according to the current workflow your project uses. To learn more read When do automatic timers start / stop?

Is it compatible with Tempo?

down arrow icon

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.

How sub-tasks are handled?

down arrow icon

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.

How does it calculate time worked?

down arrow icon

If you want to know more about the way we calculate time please check out How time spent is calculated (with working hours)?

When time is logged into Jira?

down arrow icon

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.