Tempo Teams on Cloud vs Server/Data Center

While the UI of Tempo Teams is the same for both the Cloud and Server/DC versions, the basic features are actually structured differently. Certain features on Server/DC such as Team Timeline, Program Boards, Team Utilization, Link to Jira Boards have either not been migrated to Cloud, or have been deprecated from Cloud.

Similarities:

As mentioned above, the UI of Tempo Teams is the same on Cloud as on Server/DC. Each Team can only have one Team lead. A Tempo Team can be linked to multiple Jira projects, but only one team can be linked to an issue at a time since there is only one Tempo Team field in Jira issues. Team Programs (a team of teams) are also available on both hosts.

Differences:

On Cloud, when adding team members in bulk via a Jira user group, users are added individually. On Server/DC, a Jira user group is added as a single entity with the users at that time. The group added to a Tempo Team is NOT synced live with the original Jira user group, so you must manually remove it and add it again to the Tempo Team to keep up with membership changes.

Team Roles are not used as much on Cloud as on Server/DC because the Tempo Account Price Table is not migrated to Cloud.

Team member commitment is calculated in the capacity report and team utilization on Server/DC. On Cloud, it’s only a simple labeling function: a team member’s utilization (U%) is calculated based on logged hours/required hours.

Generic Resources for Tempo Planner is available in the Resource Planning UI for both Cloud and Server/DC. Generic resource data is available in Tempo Reports and Exports on Cloud, but the data is not available in reports or exports on Server/DC.

The Capacity Report has both a UI report and export data on Server/DC, whereas there is only the exported raw data on Cloud.

What’s available on one but not the other: