Yes. We have decided to update our handling of API requests by deprecating the API Servlet at the end of this year. Instead, you will communicate to Tempo via REST APIs. This means the Servlet API won't be available for our cloud version for JIRA after we have deprecated it. These changes should not affect your daily work as you will not notice the transition period upon migration to the new version. Below you will find a table that will take you to more information about each feature that has now been deprecated and how you can retrieve this information either with the Tempo REST API or the JIRA REST API.
|Theme||Feature being deprecated||Announced on|
|Servlet APIs||updateWorklogs||June 6, 2017|
|getWorklogReport||June 6, 2017|
|billingKeyList||June 6, 2017|
|holidayList||June 6, 2017|
|JIRA fields||June 6, 2017|
|format=excel||June 6, 2017|
The updateWorklogs servlet API is not a highly used feature and we feel that it is not our responsibility to check if worklogs have been modified since they were last exported to an external system. That external system should be responsible for handling these sorts of use cases, which is why the feature is being deprecated.
The getWorklogReport servlet API is not a highly used feature, which is why it is being deprecated.
While the billingKeyList servlet API is being deprecated, it is possible to use the TEMPO REST API to retrieve this information, as it consists of a list of available accounts to be used when creating reports.
For example, the string below retrieves all accounts that the logged-in user has permission to browse:
Following the development of a new version of Tempo Cloud for JIRA, we have decided to deprecate the HolidayList API, which until had been a part of the Servlet API. The HolidayList returned a list of registered non-working days (holidays) to be used when calculating required hours in an external system.
From now on, communications to Tempo will go through REST APIs.
The following JIRA fields are no longer supported in the getWorklogs service. They can be retrieve using JIRA REST APIs.