Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

The majority of features are comparable between Tempo Planner 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

Planner Server/Data Center

Planner Cloud

Alternative

Data retention (managed by local server for Server/DC; AWS for cloud)

(tick)

Cloud security

Data storage

Local: alongside Jira

Cloud hosted: AWS - US Eastern

Capacity Report

(tick)

(tick)

Use the Exporting User Capacity in Planner Cloud to export your team's planned time and availability. A report based on this exported data is underway and will be available shortly.

Manage staff

(tick)

(lightbulb)

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

Staff location

(tick)

(lightbulb)

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

Resource Skills

(tick)

Generic Resources

(tick)

(tick)

Generic Resources in Planner Cloud can be included in reports and in exported data.

Team Planning on Epics

(tick)

Team Timeline

(tick)

(tick)

Team Timeline was deprecated in Planner Cloud and replaced by Team Planning on Epics.

Settings

Tempo Accounts - configure label

(tick)

Not available in Planner Cloud due to Jira Cloud limitations.

Tempo Teams - configure label

(tick)

Not available in Planner Cloud due to Jira Cloud limitations.

Support for Jira groups for Team members

(tick)

Limited

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

Support for Jira groups for Team permission roles

(tick)

Populate Tempo permission groups with selected users. Vote for this idea in https://ideas.tempo.io/ideas/T-I-1986 .

Permission Roles across Teams

(tick)

Compressed view

(tick)

Jira custom fields

Tempo Team

(tick)

(tick)

Team Role

(tick)

(tick)

Create a custom Jira custom field which collects data from the Team role REST API. (Needs an additional add-on)

Integrations

Tempo mobile app

(tick)

(tick)

Identical user interface but login authentication methods are different in Planner Cloud.

Calendar integration (Google Calendar, Office 365)

(tick)

  • No labels