...
Functionality | Planner Server/Data Center | Planner Cloud | Alternative |
---|---|---|---|
Data retention (managed by local server for Server/DC; AWS for cloud) | ⛔ |
| |
Data storage | Local: alongside Jira | Cloud hosted: AWS - US Eastern | |
|
| 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. | |
|
| Vote for this idea in https://ideas.tempo.io/ideas/T-I-438 . | |
|
| Vote for this idea in https://ideas.tempo.io/ideas/T-I-1617 . | |
⛔ |
| ||
|
| Generic Resources in Planner Cloud can be included in reports and in exported data. | |
⛔ |
| ||
Team Timeline |
|
| Team Timeline was deprecated in Planner Cloud and replaced by Team Planning on Epics. |
Settings | |||
| ⛔ | Not available in Planner Cloud due to Jira Cloud limitations. | |
| ⛔ | Not available in Planner Cloud due to Jira Cloud limitations. | |
| Limited | Team members can be added from Jira groups but need to be maintained manually. | |
| ⛔ | Populate Tempo permission groups with selected users. Vote for this idea in https://ideas.tempo.io/ideas/T-I-1986 . | |
⛔ |
| ||
⛔ |
| ||
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 | |||
|
| Identical user interface but login authentication methods are different in Planner Cloud. | |
Calendar integration (Google Calendar, Office 365) | ⛔ |
|