Skip to main content
Skip table of contents

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.

(tick) = available

⛔ = not available

(lightbulb) = 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

(tick)

(tick)

The user interface for My work list and Calendar view is different on Cloud and Server/DC.

Timesheet View

(tick)

(tick)

Automated Suggestions

(tick)

Automated suggestions are available for Jira, Google, Office365, GitHub, JetBrains, VS Code.

Prevent users from logging time on parent issues

(tick)

Vote for this idea in https://ideas.tempo.io/ideas/T-I-639

Allow users to log time on non-editable issues

(tick)

Internal Issues

(tick)

(tick)

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

(tick)

Tracking Time

Tempo Tracker for Jira Issues

(tick)

(tick)

Access and UI for the Cloud tracker are different, but the core functionality is the same.

Managing Teams

Permission Roles across Teams

(tick)

 

View issue hours

(tick)

Support for Jira groups for Team Members

(tick)

Limited

Members can be added from Jira groups but need to be maintained manually.

Support for Jira groups for Team permission roles

(tick)

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

(tick)

(tick)

Staff Location

(tick)

(lightbulb)

Vote for this idea in https://ideas.tempo.io/ideas/T-I-1617

Staff ID

(tick)

(lightbulb)

Vote for this idea in https://ideas.tempo.io/ideas/T-I-74

Tempo Accounts

Configure Label

(tick)

(tick)

Account field on sub-issues set by parent issue

(tick)

(lightbulb)

Vote for this idea in https://ideas.tempo.io/ideas/T-I-639

Tempo Apps

Servlet API

(tick)

Cloud REST APIs

Chrome Extension

(tick)

Slack Integration

(tick)

VS Code (Visual Studio) Integration

(tick)

Event handlers (Timesheet approvals, Accounts, Worklog attributes, Teams)

(tick)

(tick)

Cloud provides webhooks.

Tempo mobile app

(tick)

(tick)

Tempo Gadgets

Tempo Gadgets and Dashboards

(tick)

(tick)

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)

(tick)

Cloud Security

Price Rates

(tick)

Rates in Cost Tracker

Billable Hours

(tick)

(tick)

On Cloud, this is configured for each project with project permission schemes.

Issue Expenses

(tick)

Expenses in Cost Tracker

Dynamic Dropdown lists for work attributes

(tick)

Personalized Date and Time Format

(tick)

In Server, you can set personal date and time format, whereas Cloud has a Global setting.

Bulk Operations

Bulk Deleting worklogs

(tick)

Bulk Editing worklogs - billable hours and account work attribute

(tick)

Bulk moving worklogs

(tick)

Tempo Reports

Utilization Report

(tick)

(lightbulb)

Vote for this idea in https://ideas.tempo.io/ideas/T-I-143

Time and Expenses Report

(tick)

Cost Tracker

Revenue Report

(tick)

Cost Tracker

Export to PDF

(tick)

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.