Tempo Timesheets Server/Data Center vs. Cloud
Overview of the similarities and differences between Tempo Timesheets Server/Data Center and Cloud
The majority of features are comparable between Tempo Timesheets Server/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.
= available
= not available
= in development and/or on our product roadmap
Functionality | Timesheets Server/Data Center | Timesheets Cloud | Alternative |
|---|---|---|---|
Integrations | |||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
Event handlers (Timesheet approvals, Accounts, Worklog attributes, Teams) |
|
| |
Event handlers (worklogs) |
|
| |
|
| ||
Reports | |||
|
| Tempo Reports will support group by Account Category and Account Category Type as well as Teams | |
|
| Cost Tracker | |
|
| Cost Tracker | |
Configuration | |||
|
| On Cloud this is configured for each project with project permission schemes | |
|
| ||
Data retention (managed by customer external to the application) |
|
| |
Data storage | Local: alongside Jira | Cloud hosted: AWS - US Eastern | Tempo is exploring data hosting options in Europe. |
|
| ||
|
| ||
|
| ||
| Limited | Members can be added from Jira groups but need to be maintained manually | |
|
| Populate Tempo permission groups with selected users | |
|
| Cost Tracker | |
|
| Cost Tracker | |
|
| ||
Logging time - option to prevent users from logging time on parent issues |
|
| |
Logging time - option to allow users to log time on non-editable issues |
|
| |
|
| ||
|
| ||
|
| Currently possible on Cloud using Project Automation (Atlassian tool) | |
|
| Need to recreate in Cloud | |
|
| Whereas internal issues in Tempo Server overwrite Jira project permissions schemes (and allow users to track time without having the permission to view others' worklogs), internal issues in Tempo Cloud only provide the functionality of a quick link. The use case from Server can only be recreated using Jira and Tempo permissions. | |
Jira custom fields | |||
Accounts |
|
| |
Teams |
|
| |
Team role |
|
| Create a custom Jira custom field which collects data from the Team role REST API. (Needs an additional add-on) |
Time tracking | |||
Tempo tracker for Jira issues |
|
| Access and UI for the Cloud tracker is different but the core functionality is the same |
Automated suggestions for time records |
|
|