Time Tracker (DC)

Differences between Time Tracker DC and Time Tracker Cloud

The majority of features are comparable between the Time Tracker Data Center (DC) and Cloud applications. To help you understand the differences between our Data Center and Cloud products for Time Tracker, we have gathered the comparison information below, which outlines where key functionalities diverge.

Quick Summary

Time Tracker’s Cloud application is best if you want the Rovo AI assistant, the newest features, broad gadget coverage, and a managed (no-server) admin model. Cloud is where Tempo is actively investing.

Time Tracker’s DC application is best if you need server-side control, the workedIssues() JQL function, the legacy REST API and plugin endpoints, and the Project Pivot gadget.

High-Level Comparison

Dimension

Time Tracker DC

Time Tracker Cloud

Hosting / platform

Jira Data Center (self-managed server)

Jira Cloud, on Forge (migrated from Connect in Dec 2025)

Time logging

Popup, inline timer, edit/delete, CSV import

Same as DC plus:

Quick Time Entry, log-for-others, work-logging automation, Rovo agent (Time Tracker Assistant)

Report types

Versions older than 6.0.0:

Timespent, Timesheet, Project Pivot

6.0.0+:
Full 13-report set via Flexible Reports

Full 13-report set

Dashboard gadgets

Versions older than 6.0.0:
4 gadgets (Timesheet, Project Pivot, Timespent, Worked Time Chart)

6.0.0+: 13 gadget versions across the 13 reports

Gadget versions across its 13 reports

Project Pivot is the one DC-exclusive gadget

Cost reporting

6.0.0+:
Hourly rates + PDF invoice via Flexible Reports

Hourly rates + PDF invoice

Email subscriptions

Yes, but not for Flexible Reports

Yes

Rovo agent / AI assistant

Not available

Time Tracker Assistant (Rovo agent)

REST API

Jira API v2 + legacy plugin endpoints

Note: Flexible Reports are not supported by REST API.

Jira API v3 only (Time Tracker API deprecated)

workedIssues() JQL function

Yes

No

Admin model

Server-side (Jira Manage Apps), config audit log

Per-tenant managed settings, config audit log

Permission model

Auditor Groups + Auditor Roles + Restricted Groups + Time Entry Panel (6.0.0+ via Flexible Reports)

Auditor Groups + Accountants Groups + Time Entry Panel (groups/projects)

Feature Comparison

Time Logging

Capability

DC

Cloud

Notes

Log Work Done popup (issue key + time spent)

Cloud popup smaller on Forge; extra fields under "More options"

Quick Time Entry ("+" inline into Spent field)


Inline timer (start / pause / save)

Lives in Time Entry report / Timesheet gadget

Edit existing worklog

Cloud can't change the associated issue on edit

Delete worklog


Log work from Jira issue view (panel)

Cloud panel hidden until enabled

Copy link to Log Work popup


Log work on behalf of others


Work-logging automation (auto-suggest by end of day)


CSV worklog import (importTimesheet.csv)

Both: Key + Time Spent required; optional date/comment

Reports

The Time Tracker Cloud application includes all 13 reports.

On Time Tracker DC, only Timesheet and Timespent were available before DC version 6.0.0 (alongside the DC-only Project Pivot report). The other 11 reports were added in DC 6.0.0 and are marked "6.0.0+" in the table below. On DC 6.0.0+, these reports are delivered through Flexible Reports.

Note: Subscribing to reports by email is not available for the DC Flexible Reports (6.0.0+), and these reports are not supported by the REST API.

Report

DC

Cloud

Notes

Time Entry

✅ 6.0.0+ as part of Flexible Reports

Daily logging interface with timer

Timesheet

✅ all versions

Day-by-day workload view

Calendar

✅ 6.0.0+ as part of Flexible Reports

Not exportable (both)

Timespent

✅ all versions


Pivot by User

✅ 6.0.0+ as part of Flexible Reports


Pivot by Status

✅ 6.0.0+ as part of Flexible Reports


Pivot by Label

✅ 6.0.0+ as part of Flexible Reports


Time Tracking (estimate vs. actual)

✅ 6.0.0+ as part of Flexible Reports

Configurable columns

Pie Chart

✅ 6.0.0+ as part of Flexible Reports

Not exportable (both)

Time in Status

✅ 6.0.0+ as part of Flexible Reports

From change history; honors working/break-time settings

Resolution Time

✅ 6.0.0+ as part of Flexible Reports


Time Balance

✅ 6.0.0+ as part of Flexible Reports

Time spent, estimate, variance, progress

Cost

✅ 6.0.0+ as part of Flexible Reports (report only)

No cost gadget on DC.

Project Pivot

✅ all versions

Project Pivot is the one DC-exclusive gadget

Report Operations

Capability

DC

Cloud

Notes

Export to CSV (.csv)


Export to Excel (.xls)


PDF invoice export (Cost report)


Print reports

✅ (browser → Save as PDF)


Shareable export/download URLs

⚠️ via Save & Share

DC offers raw download links for embedding in wikis

Save & share custom reports

✅ 6.0.0+ as part of Flexible Reports

Cloud has explicit Save & Share with per-user sharing

Email report subscriptions (scheduled)

✅ (not for Flexible Reports)

DC 6.0.0+ Flexible Reports can't be emailed. Cloud: "send only if timesheet incomplete" reminder option

Dashboard Gadgets

Both products ship dashboard gadgets. Time Tracker Cloud offers gadget versions across its 13 reports, whereas Time Tracker DC ships 4 gadgets. The only gadget unique to DC is Project Pivot.

The 4 DC gadgets below reflect versions before DC version 6.0.0. For version 6.0.0 and after, DC consolidates the gadgets into a single multi-report gadget.

Gadget

DC

Cloud

Notes

Timesheet / Time Sheet

✅ all versions

Log/edit directly from gadget

Timespent

✅ all versions


Pie Chart / Worked Time Chart

✅ (Worked Time Chart) all versions

✅ (Pie Chart)

Same capability, different name per platform

Project Pivot

✅ all versions

DC-exclusive; legacy report/gadget, still in current DC

Time Entry, Calendar, Pivot by User / Status / Label, Time Tracking, Time In Status, Resolution Time, Time Balance, Cost

✅ 6.0.0+ as part of Flexible Reports


Administration and Configuration

Capability

DC

Cloud

Notes

Where admin lives

Jira → Manage Apps → Time Tracking (server-side)

Per-tenant app settings


General settings (log behavior, working hours, descriptions, labels)


User default settings (reporting day, week type, formats, columns)


Per-user preferences (no admin needed)


Holidays management

✅ + ICS/URL import

DC supports calendar import; Cloud has one-time + annual recurring

Hourly rates engine


Disable logging for projects/groups


Disable subscriptions


Config audit log (last 30 changes)


Set as Jira's time-tracking provider

Only true or false, nothing to configure


Permissions and Access

Capability

DC

Cloud

Notes

Auditor groups (view others' time)

"Auditors Groups" on both

Auditor roles (project-role based)

"Auditors Roles" — supported on Cloud and DC

Restricted groups (same-group visibility only)

"Restricted Groups" — supported on Cloud and DC

Accountants group (Cost report access)

⚠️ via rates/auditor

✅ explicit

Cloud: "Accountants Groups"

Log work for others (groups)

Cloud: "Log Work For Others Groups"

Time Entry panel access (groups / projects)

✅ Configuration exists in 6.0.0+ as part of Flexible Reports

Cloud: "Time Entry Issue Panel Groups" + "Time Entry Issue Panel Projects"

Default worklog visibility (group / role)

✅ Configuration exists in 6.0.0+ as part of Flexible Reports

Cloud: baseline "Default Worklog Visibility Group / Role"

Integrations, API and AI

Capability

DC

Cloud

Notes

Time Tracker Assistant (Rovo AI agent)

Analyzes Jira activity, suggests & logs work, generates report links; logged-in user only

workedIssues() JQL function

DC advanced search across boards/filters/dashboards

REST API for worklogs

✅ Jira API v2

Note: Flexible Reports are not supported by REST API.

⚠️ Jira API v3

Tempo's own Time Tracker REST API deprecated on Cloud (Nov 2025). DC Flexible Reports (6.0.0+) aren't exposed via REST API.

Legacy plugin endpoints (/rest/timesheet-gadget/1.0/...)

DC: UNIX-ms dates, seconds-based timeSpent, csvExport param

Time Tracker → Tempo Timesheets integration

n/a

❌ deprecated

One of two features Cloud has deprecated

Time Tracker DC to Time Tracker Cloud Migration Considerations

If your goal is to move from Time Tracker DC to Time Tracker Cloud, the following are the main parity gaps between the two applications:

  • Custom integrations
    DC's Jira API v2 + /rest/timesheet-gadget/ endpoints don't exist on Cloud. They must be rebuilt on Jira API v3. Plan development time accordingly.

  • workedIssues() JQL
    Any saved filters, boards, or automations that use this function won't carry over. You must find an equivalent or rework those filters.

  • Project Pivot gadget
    This is the only gadget that is exclusive to DC. If your DC dashboards use it, it must be rebuilt from Cloud's Pivot by User report/gadget. Cloud's overall gadget coverage is broader.

  • Forge field config
    Time Tracker Cloud moved to Forge in Dec 2025. If moving from DC to Cloud, old bookmarks/links will break, and the "Log Work" field will need to be re-added to each project's field configuration, otherwise worklogs won't show.

  • Time Tracker REST API
    Time Tracker's own REST API was deprecated on Cloud in Nov 2025. Cloud integrations now go through the Jira REST API v3. DC still uses Jira REST API v2 + legacy /rest/timesheet-gadget/1.0/ plugin endpoints, so any custom integration you built on DC will need to be reworked.

  • Admin model differs
    DC configuration resides in Jira's Manage Apps (server-side). Cloud configuration settings are managed per-tenant.