Most features are comparable between Tempo Timesheets Data Center and Cloud, and we are continually working to ensure the parity between the two products moves that much closer.
As you consider the best options for migration and to help you understand the main differences between the two versions, we’ve put together the following table to show where key functionalities diverge.
⛔ = not available
For more details on some key features, see Data Center vs Cloud: Detailed Feature Comparisons .
|
Functionality |
Timesheets Data Center |
Timesheets Cloud |
Alternative |
|---|---|---|---|
|
Logging Time |
|
|
|
|
|
|
The user interface for My work list and Calendar view is different on Cloud and DC. |
|
|
Timesheet View |
|
|
|
|
⛔ |
|
Automated suggestions are available for Jira, Google, Office365, GitHub, JetBrains, VS Code. |
|
|
|
⛔ |
Vote for this idea in https://ideas.tempo.io/ideas/T-I-639 |
|
|
|
⛔ |
|
|
|
|
|
Whereas internal issues in Tempo Data Center overwrite Jira project permissions schemes (and allow users to track time without having permission to view others' worklogs), internal issues in Tempo Cloud only provide the functionality of a quick link. The use case from Data Center can only be recreated using Jira and Tempo permissions. |
|
|
⛔ |
|
|
|
|
Tracking Time |
|
|
|
|
Tempo Tracker for Jira Issues |
|
|
Access and UI for the Cloud tracker are different, but the core functionality is the same. |
|
Managing Teams |
|
|
|
|
⛔ |
|
|
|
|
⛔ |
|
|
|
|
|
Limited |
Members can be added from Jira groups but need to be maintained manually. |
|
|
|
⛔ |
DC adds Jira group as a single unit. Cloud adds all users from Jira group individually. Vote for this idea in https://ideas.tempo.io/ideas/T1-I-54 |
|
|
|
|
|
|
|
|
|
Vote for this idea in https://ideas.tempo.io/ideas/T-I-1617 |
|
|
|
|
Vote for this idea in https://ideas.tempo.io/ideas/T-I-74 |
|
|
Tempo Accounts |
|
|
|
|
|
|
|
|
|
|
|
Vote for this idea in https://ideas.tempo.io/ideas/T-I-639 |
|
|
Tempo Apps |
|
|
|
|
|
⛔ |
||
|
⛔ |
|
|
|
|
⛔ |
|
|
|
|
⛔ |
|
|
|
|
Event handlers (Timesheet approvals, Accounts, Worklog attributes, Teams) |
|
|
Cloud provides webhooks . |
|
|
|
|
|
|
Tempo Gadgets |
|
|
|
|
Tempo Gadgets and Dashboards |
|
|
|
|
Configuration |
|
|
|
|
Local: alongside Jira |
Cloud hosted: AWS - US Eastern and Europe |
|
|
|
Data Retention (managed by local server for DC; AWS for cloud) |
⛔ |
|
|
|
|
|
||
|
|
|
On Cloud, this is configured for each project with project permission schemes . |
|
|
|
⛔ |
||
|
|
|
Dynamic Dropdown for Cloud functions very closely to the Data Center version. |
|
|
⛔ |
|
In Data Center, you can set personal date and time format, whereas Cloud has a Global setting. |
|
|
Bulk Operations |
|
|
|
|
|
|
|
|
|
Bulk Editing worklogs - billable hours and account work attribute |
⛔ |
|
|
|
⛔ |
|
|
|
|
Tempo Reports |
|
|
|
|
|
|
Vote for this idea in https://ideas.tempo.io/ideas/T-I-143 |
|
|
|
⛔ |
||
|
|
⛔ |
||
|
⛔ |
|
|