Tempo Timesheets Server/Data Center vs. Cloud

Most 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

= future consideration

For more details on some key features, see Server/Data Center vs Cloud: Detailed Feature Comparisons.

Functionality	Timesheets Server/Data Center	Timesheets Cloud	Alternative
Logging Time
My Work Calendar View			The user interface for My work list and Calendar view is different on Cloud and Server/DC.
Timesheet View
Automated Suggestions	⛔		Automated suggestions are available for Jira, Google, Office365, GitHub, JetBrains, VS Code.
Prevent users from logging time on parent issues		⛔	Vote for this idea in https://ideas.tempo.io/ideas/T-I-639
Allow users to log time on non-editable issues		⛔
Internal Issues			Whereas internal issues in Tempo Server 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 Server can only be recreated using Jira and Tempo permissions.
Viewing users with no hours logged	⛔
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
Permission Roles across Teams	⛔
View issue hours	⛔
Support for Jira groups for Team Members		Limited	Members can be added from Jira groups but need to be maintained manually.
Support for Jira groups for Team permission roles		⛔	Server/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
Manage staff
Staff Location			Vote for this idea in https://ideas.tempo.io/ideas/T-I-1617
Staff ID			Vote for this idea in https://ideas.tempo.io/ideas/T-I-74
Tempo Accounts
Configure Label
Account field on sub-issues set by parent issue			Vote for this idea in https://ideas.tempo.io/ideas/T-I-639
Tempo Apps
Servlet API		⛔	Cloud REST APIs
Chrome Extension	⛔
Slack Integration	⛔
VS Code (Visual Studio) Integration	⛔
Event handlers (Timesheet approvals, Accounts, Worklog attributes, Teams)			Cloud provides webhooks.
Tempo mobile app
Tempo Gadgets
Tempo Gadgets and Dashboards			Cloud has Account, Teams, and User Gadgets.
Configuration
Data Storage	Local: alongside Jira	Cloud hosted: AWS - US Eastern	Tempo is exploring data hosting options in Europe.
Data Retention (managed by local server for Server/DC; AWS for cloud)	⛔		Cloud Security
Price Rates		⛔	Rates in Cost Tracker
Billable Hours			On Cloud, this is configured for each project with project permission schemes.
Issue Expenses		⛔	Expenses in Cost Tracker
Dynamic Dropdown lists for work attributes		⛔
Personalized Date and Time Format	⛔		In Server, you can set personal date and time format, whereas Cloud has a Global setting.
Bulk Operations
Bulk Deleting worklogs	⛔
Bulk Editing worklogs - billable hours and account work attribute	⛔
Bulk moving worklogs	⛔
Tempo Reports
Utilization Report			Vote for this idea in https://ideas.tempo.io/ideas/T-I-143
Time and Expenses Report		⛔	Cost Tracker
Revenue Report		⛔	Cost Tracker
Export to PDF	⛔