Tempo Teams’ While the UI of Tempo Teams is the same for both the Cloud and Server/DC versions, the basic features are actually structured differently on Cloud than on Server/DC. Certain features are not migrated or deprecated on Cloud, but they are remained 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:
Teams' UI is exactly 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 and can link . A Tempo Team can be linked to multiple Jira projects. One , but only one team can only be linked to one issue. Programs 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 platformshosts.
Differences:
Teams on Cloud
Bulk add members
Team Roles, but not with Tempo Accounts
Member Commitment as is a label
Generic Resource Resources in Reports/Exports
Capacity Report in Reports/Exports
Teams on Server/DC
Jira user groupgroups
Roles with Tempo Accounts
Member Commitment is calculated in for Utilization/Capacity
Generic ResourceResources, but not in Reports
Capacity Report in Exports
When On Cloud, when adding team members by in bulk via a Jira user group, users are added individually on Cloud. On Server/DC, a 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 keep it up-to-dateat 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 of the Tempo Account Price Table is not migrated over to Cloud.
Team member commitment is calculated in the capacity report and team utilization on Server/DC. On Cloud, but it’s only a simple labeling function on Cloud, where user’s : 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 platforms. However, its Cloud and Server/DC. Generic resource data is available in Tempo Reports and Exports on Cloud, but it’s 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, where whereas there is only the exported raw data on Cloud.
What’s available on one but not the other:
Tempo Teams on Cloud
Permission Roles across Teams
Skills (with Tempo Planner)
Tempo Teams on Server/DC
Team Timeline
Team Utilization
Location
Staff ID
Manage Staff
Link to Jira Boards
Program Board
Configurable custom field label