Versions Compared

Old Version 9

changes.mady.by.user Susan Wu

Saved on

compared with

New Version Current

changes.mady.by.user Susan Wu

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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 and , 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 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, 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:

Tempo Teams on Cloud

  1. Bulk add members

  2. Team Roles, but not with Tempo Accounts

  3. Member Commitment as is a label

  4. Generic Resource Resources in Reports/Exports

  5. Legacy Capacity Report in Reports/Exports

Teams on Server/DC

  1. Resource Planning

  2. Team Role is a Tempo field

Tempo Teams on Data Center

  1. Jira user groupgroups

  2. Roles with Tempo Accounts

  3. Member Commitment is calculated in for Utilization/Capacity

  4. Generic ResourceResources, but not in Reports

  5. Legacy Capacity Report in Exports

When

  1. Teams

  2. Team Role is a Jira custom field

Here are some more details about each of these options:

by on Cloud

  • . On

Server/DC

  • Data Center, 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-date.

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.

Team

  • 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

Server/DC, but it’s

  • Data Center. On Cloud, 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 Planner

is

  • are available in the Resource Planning

(

  • UI

)

  • for both

platforms. However, its it’s on Server/DC has both UI report and export data on Server/DC, where there is only exported raw data on Cloud.

  • 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

  1. Permission Roles across Teamsmultiple teams

  2. Skills (with Tempo Planner)

  3. Capacity Report Export with Generic Resources, Skills and FTE (Full Time Equivalent)

  4. Deactivated Jira users automatically with leaving date for all teams

Tempo Teams on

Server/DC

Data Center

  1. Team Timeline

  2. Team Utilization

  3. Location

  4. Staff ID

  5. Manage Staff

  6. Link to Jira Boards

  7. Program Board

  8. Program Capacity Reports

  9. Configurable custom field label

  10. Team Roles included in export report

  11. Capacity in Reports