Tempo Teams’ While the UI of Tempo Teams is the same for both the Cloud and Data Center 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, on Data Center 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:
Teams' UI is exactly As mentioned above, the UI of Tempo Teams is the same on Cloud as on Server/DCData Center. 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:
Tempo 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
Legacy Capacity Report in Reports/Exports
Resource Planning
Team Role is a Tempo field
Tempo Teams on Data Center
Jira user groupgroups
Roles with Tempo Accounts
Member Commitment is calculated in for Utilization/Capacity
Generic ResourceResources, but not in Reports
Legacy Capacity Report in Exports
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
Data Center, a Jira user group is added as a single entity with the users
Team Roles are not used as much on Cloud as on Server/DC because of Tempo Account Price Table is not migrated over to Cloud.
Teamat 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 member commitment is calculated in the capacity report and team utilization on
Data Center. 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 Data Center. Generic resource data is available in Tempo Reports and Exports on Cloud, but
the data is not available
is available on both platforms with a minor difference: commitment % is calculated on Data Center, but not on Cloud. Effective Team Size is available only on Data Center. The timeframe can be daily/weekly/monthly/quarterly on Data Center, but only monthly on Cloud.
Team Role can be included in the export report on Data Center 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 Teamsmultiple 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/DCData Center
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
Capacity in Reports