2021-01-19 | Tempo Budgets for Server 14.0 Release

This latest major version of Tempo Timesheets features changes to the Jira SPI and Jira REST API. This results in the Tempo Team custom field being returned as an object rather than as a string and also makes it possible to update the Jira SPI with an object. While it is still possible to use the existing Jira REST API endpoints to update the team custom field with name or ID, it is no longer possible to use the Jira SPI to do so. 

The goal in making these changes is to give you more flexibility when integrating with the Tempo Team custom field through the Jira SPI and API interfaces, and to allow those of you who use these interfaces to simplify your third party integrations. These changes will return a Team object that includes both the team name and the team ID (instead of just the team ID), which will allow you to access more information when you use the Jira SPI and REST API interfaces.

Please note that these changes may have an impact on third party apps and integrations within your organization. We recommend that you confirm that your critical third party apps are compatible with this change before upgrading.

You can find more technical information about these changes here. We have also compiled information to help you understand how to update the team custom field in ScriptRunner scripts.

IMPROVEMENTS

• Tempo Team custom field is now returned as an object (rather than a string) that includes both the team name and the team ID.
• CSV exports of Jira issue data now include team name instead of team ID in the Team field. This applies to data exported to CSV from Tempo’s Logged Time report as well as data exported to CSV directly from Jira.
• Deprecation warning: Private endpoint rest/tempo-core/1/users/search is being deprecated and slated for removal