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, and 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:
Tempo Teams on Cloud
Bulk add members
Team Roles, but not with Tempo Accounts
Member Commitment is a label
Generic Resources in Reports/Exports
Legacy Capacity Report in Resource Planning
Team Role is a Tempo field
Tempo Teams on Server/DC
Jira user groups
Roles with Tempo Accounts
Member Commitment is calculated for Utilization/Capacity
Generic Resources, but not in Reports
Legacy Capacity Report in Teams
Team Role is a Jira custom field
Here are some more details about each of these options:
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 Planner are 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.
Legacy Capacity Report is available on both platforms with a minor difference: commitment % is calculated on Server/DC, but not on Cloud. Effective Team Size is available only on Server/DC. The timeframe can be daily/weekly/monthly/quarterly on Server/DC, but only monthly on Cloud.
Team Role can be included in the export report on Server/DC because it’s a Jira custom field. On Cloud, Team role is a Tempo field and it’s not included in the export report.
What’s available on one but not the other:
Tempo Teams on Cloud
Permission Roles across multiple teams
Skills (with Tempo Planner)
Capacity Report Export with Generic Resources, Skills and FTE (Full Time Equivalent)
Deactivated Jira users automatically with leaving date for all teams
Tempo Teams on Server/DC
Team Timeline
Team Utilization
Location
Staff ID
Manage Staff
Link to Jira Boards
Program Board
Program Capacity Reports
Configurable custom field label
Team Roles included in export report