Knowledge Base Articles

Time Tracker vs Timesheets on Data Center

Feature Differences

Summary: On Data Center, Timesheets is Tempo's full time-tracking, approval, and reporting product (My Work, Timesheet view, approvals, Tempo Accounts, Teams, mobile app). Time Tracker is the entry-level app that extends Jira's built-in time tracking with configurable reports and gadgets. Time Tracker DC has no approvals.

At a glance

Area

Tempo Timesheets (DC)

Time Tracker (DC)

Positioning

Logging, approvals, Accounts, Teams, and reporting. Per Timesheets by Tempo on Cloud vs on Data Center, core features are the same as Cloud, with some differences.

Lightweight reporting and gadgets on Jira hours. Best if you need server-side control, the workedIssues() JQL function, the legacy REST API, or the Project Pivot gadget (Differences between Time Tracker DC and Cloud).

Hosting

Jira Data Center

Jira Data Center, server-side (Manage Apps)

Logging time

My Work, Log Time form, one running Tempo Tracker per user

Log Work popup, inline timer, edit and delete, CSV import, log work from the issue view

Approvals

Yes, Timesheet Approval in My Work. Project time approvals not on DC, per the Cloud vs DC KB.

No approvals function (Tempo blog)

Teams

Yes, Tempo Teams

Access is by Jira groups (Auditor Groups, Restricted Groups, Auditor Roles)

Accounts

Yes, Accounts and work attributes

Not applicable

Reporting

Logged Time reports.

13 reports on DC 6.0.0+ through Flexible Reports. Before 6.0.0, only Timesheet, Timespent, and Project Pivot. (Differences)

Dashboard gadgets

14 gadgets, per the Cloud vs DC KB

4 gadgets before 6.0.0. From 6.0.0, one multi-report gadget covers the 13 reports. Project Pivot is DC-only.

Permissions

Tempo permissions

Auditor Groups, Auditor Roles, Restricted Groups, Time Entry Panel (6.0.0+)

Admin configuration

Jira → Manage Apps ->Tempo.

Jira → Manage Apps → Time Tracking. Config audit log (last 30 changes).

Mobile

Tempo Mobile App uses Basic Auth on DC, per the Cloud vs DC KB

Not applicable

Integrations and API

Tempo Servlet API and Event handlers, per the Cloud vs DC KB

Jira REST API v2 plus legacy /rest/timesheet-gadget/1.0/ endpoints. Flexible Reports (6.0.0+) are not exposed through the REST API.

AI

Not available on DC

Not available on DC

Time Tracker DC reports

Timesheet, Timespent, and Project Pivot on all versions. From 6.0.0, the other reports are added through Flexible Reports: Time Entry, Calendar, Pivot by User, Pivot by Status, Pivot by Label, Time Tracking, Pie Chart, Time in Status, Resolution Time, Time Balance, and Cost. Flexible Reports cannot be emailed as subscriptions. Source: Reports and the differences article.

Timesheets DC differences from Cloud

Per the Cloud vs DC KB:

  • DC has one Tempo Tracker per user. Cloud has multiple.

  • Billable hours are set globally on DC. Cloud sets them by space.

  • Mobile login uses Basic Auth on DC. Cloud uses SSO.

  • Gadgets: 14 on DC, 15 on Cloud.

  • Worklogs are stored in the Jira database on DC. On Cloud they are stored on the Tempo Cloud instance.

  • Worklog author is the Jira Account ID on DC. On Cloud it is Timesheets.

  • DC moves a worklog with "Move worklog". Cloud uses "Edit a worklog".

  • DC bulk-deletes worklogs. Cloud manages bulk worklogs.

  • Date and time format is personal only on DC. Cloud also has a global format.

  • Approvals on DC are Timesheet Approval in My Work. Cloud has an Approvals tab, and project approvals with Financial Manager.