Tempo Teams’ basic features are structured differently on Cloud than on Server/DC, and some features are not migrated on Cloud, such as Team Timeline and Team Utilization, Link to Jira Boards.
Similarities:
Teams' UI is exactly the same on Cloud than on Server/DC. Each Team can only have one Team lead and can link to multiple Jira projects. Program board is Programs are also available on both platforms.
Differences:
Teams on Cloud
Bulk add members
Roles, not with Tempo Accounts
Commitment as label
Generic Resource in Reports/Exports
Capacity Report in Reports/Exports
Teams on Server/DC
Jira user group
Roles with Tempo Accounts
Commitment calculated in Utilization/Capacity
Generic Resource, not in Reports
Capacity Report in Exports
When adding team members by Jira user group, users are added individually on Cloud. On Server/DC, Jira user group is added as a single entity with the users of the time added, which is NOT sync live with Jira user group. It requires to manually remove/re-add into the Team to include the users added at the later timeto keep it up-to-date.
Team Roles are not used as much on Cloud as on Server/DC because of Tempo Account Price Table is not migrated over onto to Cloud.
Team member commitment is calculated in capacity report and team utilization on Server/DC, but it’s a simple labeling function on Cloud, where user’s utilization (U%) is calculated based on logged hours/required hours.
Generic Resources for Planner is available in Resource Planning view, but it’s (UI) for both platforms. However, its data is available in Tempo Reports /and Exports on Cloud and , but it’s not available on Server/DC.
Capacity Report has both UI report and export data on Server/DC, where there is only exported raw data on Cloud.
What’s available on one but not the other:
Teams on Cloud
Permission Roles across Teams
Skills (with Planner)
Teams on Server/DC
Team Timeline
Team Utilization
Location
Staff ID
Manage Staff
Link to Jira Boards
Program Board
Configurable custom field label