Clockwork Pro vs Clockwork Free
Feature | Clockwork Automated Timesheets Pro | Clockwork Automated Timesheets Free |
|---|---|---|
Project Types | ||
|
| |
|
| |
Track Time | ||
Set automatic timers that run whenever an issue with an assignee is in an Active status or allow users to manually start and stop timers on an issue. Clockwork Pro allows you to use an unlimited number of timers. In the Free version, timers are limited to 300 per month.  Automatic timers  Manual timers |
| âš 300 timers/month |
| ⚠️ Without the ability to filter issues in the Log Work dialog using Project, Assignee, Starred or Internal filters and assigning Worklog Attributes | |
Use timers or adding your time manually. Clockwork Pro issue view is enabled by default while in the Free version it has to be made visible each time you want to log your time from this view.  Clockwork issue view |
| ⚠️ Requires adding the Clockwork view whenever you want to log your time from the issue. |
Users can view, add and edit their time in the My Work tab either from the Timesheet or Calendar view.  My Timesheet view  Calendar view |
| ⚠️ Only Timesheet view |
Integrate your Clockwork Calendar View with your Google or Outlook Calendar to view your scheduled events and quickly report time spent on them.  Google and Outlook events in Clockwork |
|
|
Add Time Spent which will automatically recalculate the Remaining Estimate. Edit the Remaining Estimate whenever you need.  Time spent and remaining estimate |
|
|
Allow selected users (scrum masters, project leads, etc.) to log work on behalf of members of their team.  Log work for others |
|
|
Timesheets & Reports | ||
You can filter or breakdown your timesheets by multiple factors including projects, users, teams, epics, issue types, custom fields, versions, custom worklog attributes and many others.  Clockwork timesheet filters  Clockwork breakdown options |
| âš No filtering or breakdown by custom fields, worklog attributes, teams, outliers or custom issue type hierarchies |
| âš Worklogs only, without the ability to select fields | |
Save a timesheet as a report to avoid entering the parameters, filters, and breakdowns each time.  Saved reports |
|
|
Create a “Billable” worklog attribute to track your team’s billable hours.  Billable time |
| |
Billing periods will give you the ability to define how often you want to work on your billing data and lock adding, editing, or removing worklogs within a locked billing period to secure your invoices' data remain correct.  Locking time edits with billing periods |
|
|
|
| |
Use built in options or set a bookmark to select a relative date range for a timesheet.  Date range options |
|
|
Improve your future time estimations by learning from live data.  Original vs remaining estimates |
|
|
Compare logged work to Working Hours to highlight if users are working more/less hours than expected.  Comparing worklogs with individual’s working hours |
|
|
Use Outliers filters to look for team members who didn’t log enough time and send them a quick email reminder to do so. .png?inst-v=5e681345-7073-40ab-9c14-67ddee83a46e) Customizable email notifications |
|
|
Configuration Options | ||
|
| |
|
| |
Enable automatic timers, manual timers or both. Set it globally or on the project level.  Time tracking modes |
| âš Global only |
Drag and drop statuses to the Active column to customize Active Statuses in a project.  Active statuses for automatic time tracking |
|
|
Track or ignore times of less than one minute. Round up to the nearest minute or the nearest quarter of an hour.  Time rounding |
| âš Global only |
|
| |
Limit options for logging future and/or past time.  Restrict time reporting in the past or future |
|
|
Add custom attributes to your worklogs to capture detailed information. Make attributes mandatory or optional. Limit options to a predefined list or allow users to create options ad-hoc.  Worklog attributes/tags |
| |
Create a “Billable” worklog attribute to track your team’s billable hours. Track billable time |
| |
Clockwork timers use Working Hours to calculate the actual time an issue was being worked on. Clockwork timers will always use the most specific calendar available (assignee, then project, then global).  Working hours |
| âš Global only |
Integrate Working Hours with Calendar apps so that holidays are not included in time worked calculations.  Holiday schemes |
| |
JQL Integration | ||
Use the timerIsRunning extension to find issues that currently have a running timer. The allTimersInHours extension returns a numeric value that can be used in relative expressions.  Running timers  Relative accumulated hours |
|
|
Compatible with the Jira worklogAuthor expression; can be used to return issues that have been worked on by a given user.  Issues search |
|
|
Show Time Spent | ||
Show the accumulated time on Jira boards for a quick view of how long the issue has been in progress.  Running timers accumulated time |
|
|
Showing Time Spent to customers on the JSM portal demonstrates that you are working on the issue, even if you don’t yet have any results to report.  JSM portal |
|
|
Prevent Transitions | ||
Can be used with Jira workflow conditions to ensure hat work has been logged on an issue before the issue can be transitioned to the next status.  Validate time has been logged |
|
|
Use a validator to ensure that work was logged in a specific status in order for an issue to be transitioned.  Validate time has been logged in a certain status |
|
|
API | ||
|
| |
Permissions | ||
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
Jira Mobile Support | ||
|
| |
Security & Support | ||
|
| |
|
| |
|
| |
|
| |
Premium | Standard | |
|
|
