Skip to main content
Skip table of contents

2020-05-12 | Tempo Planner for Server 7.16.0 Release

We've released version 7.16.0 of Tempo Planner which is compatible with Atlassian's Jira 8.x platform. This release introduces the new Tempo look. We've also made improvements to the Planned vs Actual report and fixed several bugs.



  • New Features
    • We’re excited to launch the newest iteration of the Tempo brand to our Server and Data Center customers. This includes our updated Tempo logo as well as a newly designed Tempo sidebar. These changes are part of a larger rebranding effort that we have recently implemented across the company. To make the best use of screen real estate for the content that matters most, you can now unpin the sidebar and have it show up as a hamburger menu in the upper-left corner. Read more here: Tempo is Getting a New Look.
  • Improvements
    • We've made improvements to the suggested name when saving a Planned vs Actual report.
  • Fixes

    • Fixed: Page crashes in some cases when approval period is selected in the dateRangePicker.

    • Fixed: Required field for Allocations in API Documentation is missing. 
    • Fixed: Wrong URL parameter in link from plan approval email.

    • Fixed: Team Lead cannot plan time in the Jira Issue view for team members who were added by group.

    • Fixed: A bug where the Team commitment field was not displayed when adding a member after enabling the Team planning legacy feature.

    • Fixed: Resource Planning view does not show all team members.


Upgrading Tempo Planner is free for all customers with an active Tempo license. Upgrade Tempo by using the JIRA Universal Plugin Manager (UPM).

This release is compatible with products listed in the Compatibility Page, and bundled with the following Tempo System Plugins:

Click here to view plugins bundled with this release...
  • Tempo Core 6.16.0
  • Tempo Accounts 6.16.0 Plan Core 6.16.0
  • Tempo Teams 6.16.0
  • Tempo Planning API 6.16.0
  • Tempo Budgets 13.16.0
JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.