To learn more about Tempo products, please visit our Help Center. For support, see our Support Portal.
Timesheets by Tempo on Cloud vs on Data Center
Timesheets by Tempo on Cloud has some new features that are not available on Data Center, and there are some features on Data Center that are not migrated onto Cloud due to security and infrastructure differences between the two hosts. If you have migrated from Jira Data Center to Cloud, this article will help you understand the differences in behaviour of Timesheets features between the two hosting platforms.
Similarities
The core features, Accounts and Teams, are available for Timesheets both on Cloud and on Data Center. Most of Timesheets' basic features, such as logging time, Logged Time reports, timesheet approvals, internal issues, etc. are on both platforms and are almost the same. However, there are some UI and behavioral differences as described below.
Differences on Timesheets on Cloud
New My Work UI - where users log their time, view time logged, plan time for themselves, and submit their timesheet.
New Log Time form - to log time using Timesheets by Tempo from a number of places.
Multiple Tempo Trackers instead of a single one on Data Center - to track time like a stopwatch. Start a tracker when you start working, pause it when you take a break, and log time when you’re done.
Set Billable hours is by Project instead of Globally on Data Center - to differentiate billable time from total time logged, usually for the purpose of invoicing clients.
Tempo Mobile login with SSO instead of using Basic Auth on Data Center - to use Timesheets at any time, and from anywhere on your mobile device.
15 Tempo Gadgets (Tempo Tracker) instead of only 14 gadgets on Data Center - to add Timesheets information to a Jira Dashboard where you can find quick summaries and other information that is useful to group together.
Tempo worklogs are on the Tempo Cloud instance instead of in the Jira database for Data Center - how the Tempo worklogs are stored and where located.
Timesheets as worklog author instead of Jira Account ID as worklog author for Data Center - how the Jira Account ID is used to identify individual users.
Edit a worklog instead of using “Move worklog” on Data Center - to move/change a worklog to a different Jira issue.
See more details on these differences
What’s available on one but not the other?
Timesheets on Cloud
API Integration
OAuth 2.0 Applications
Quickstart Guide with AppCues
WYSIWYG Export Reports
Timesheets on Data Center
Manage staff
Staff location
Configurable Label for Account and Team in Jira
Tempo analytics
Private API