Page Comparison

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, and some features are not migrated on Cloud, . Certain features on Data Center such as Team Timeline, Program Boards, Team Utilization and Capacity Report, 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 than on Server/DCas on Data Center. Each Team can only have one Team lead and can link . A Tempo Team can be linked to multiple Jira projects. Generic Resource feature for Planner is , 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 platformshosts.

Differences:

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 onto Cloud.

Team member commitment is used in capacity and utilization calculation on Server/DC, but it’s a simple labeling function on Cloud.

Generic Resources is available in Tempo Reports/Exports on Cloud, but not available on Server/DC yet.

• 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 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 in reports or exports on Data Center.

• Legacy Capacity Report 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: