Versions Compared

Key

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

While the UI of Tempo Teams is the same for both the Cloud and Server/DC Data Center versions, the basic features are actually structured differently. Certain features on Server/DC 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:

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

  1. Bulk add members

  2. Team Roles, but not with Tempo Accounts

  3. Member Commitment is a label

  4. Generic Resources in Reports/Exports

  5. Legacy Capacity Report in Resource Planning

  6. Team Role is a Tempo field

Tempo Teams on

Server/DC

Data Center

  1. Jira user groups

  2. Roles with Tempo Accounts

  3. Member Commitment is calculated for Utilization/Capacity

  4. Generic Resources, but not in Reports

  5. Legacy Capacity Report in Teams

  6. Team Role is a Jira custom field

Here are some more details about each of these options:

Server/DC
  • Data Center, 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 Server/DC
  • 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

Tempo
  • Planner

is
  • are available in the Resource Planning UI for both Cloud and

Server/DC Server/DC, which
  • : commitment % is calculated on

Server/DC
  • Data Center, but not on Cloud. Effective Team Size is available only

available
  • on

Server/DC
  • Data Center. The timeframe can be daily/weekly/monthly/quarterly on

Server/DC
  • Data Center, but only

available for
  • monthly on Cloud.

  • Team Role can be included in the export report on

Server/DC
  • 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 IDManage Staff

  5. Link to Jira Boards

  6. Program Board

  7. Program Capacity Reports

  8. Configurable custom field label

  9. Team Roles included in export report

  10. Capacity in Reports