Tempo Planner Server/Data Center vs. Cloud
Overview of the similarities and differences between Tempo Planner Server/Data Center and Cloud
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.
= available
= not available
= in development and/or on our product roadmap
Functionality | Planner Server/Data Center | Planner Cloud | Alternative |
|---|---|---|---|
Data retention (managed by customer external to the application) |
|
| |
Data storage | Local: alongside Jira | Cloud hosted: AWS - US Eastern | |
|
| A new updated version of the Capacity report is underway for Planner Cloud. Use the current version of the Capacity report in Planner Cloud to view your team's planned time and availability. | |
|
| ||
|
| ||
Settings | |||
|
| ||
|
| ||
| Limited | Members can be added from Jira groups but need to be maintained manually | |
|
| Populate Tempo permission groups with selected users | |
Jira custom fields | |||
Tempo Team |
|
| |
Team role |
|
| Create a custom Jira custom field which collects data from the Team role REST API. (Needs an additional add-on) |
Integrations | |||
|
|
|
