To learn more about Tempo products, please visit our Help Center. For support, see our Support Portal.

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

Tempo Teams’ basic features are structured differently on Cloud than on Server/DC, and some features are not migrated on Cloud, such as Team Timeline, Team Utilization and Capacity Report.

Similarities:

Teams' UI is exactly the same on Cloud than on Server/DC. Each Team can only have one Team lead and can link to multiple Jira projects. Generic Resource feature for Planner is available on both platforms.

Differences:

When adding team members by Jira user group, users are added individually on Cloud. On Server/DC, 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 include the users added at the later time.

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.

Capacity Report has both UI report and export data on Server/DC, where there is only exported raw data on Cloud.

What’s available on one but not the other:

Teams on Cloud

  1. Permission Roles across Teams

Teams on Server/DC

  1. Team Timeline

  2. Team Utilization

  3. Capacity Report

  4. Location

  5. Staff ID

  6. Manage Staff

  7. Link to Jira Boards

  8. Program Board

  9. Configure custom field label

  • No labels