Tempo for Server Code Deprecation and Removal

In order to minimize negative customer impact and ensure our products are of consistently the highest quality, Tempo has developed a Code Deprecation and Removal Policy to determine when and how we remove outdated code from our Server products. This policy and related communication is specifically intended to ensure that customers have ample time to prepare when we deprecate code that may have been used as a point of integration, such as:

  • Rest APIs
  • Exposed Java Services
  • Database tables
  • Java events
  • Javascript events

Generally speaking, the Code Deprecation and Removal Policy encompasses the following:

  • Tempo will remove code integration points annually in October as part of a major release.
  • Customers will be notified about the code deprecation at least 3 months in advance before the removal. This will be done via Tempo's Server Release Notes as well as other communication channels (e.g. Tempo Updates, emails and newsletter posts).
  •  Customers will be able to refer to this page to see what integration points will be targeted for the next removal.

Please note that Tempo does not provide support for code once it has been removed. 

The table below shows the code integration points which are currently targeted for deprecation and removal: 

Deprecated API Path / LocationPublic?Reason for DeprecationUse CaseAvailable WorkaroundsPlanned Removal
Java APIWorkAttributeAccessManager.validateBrowsePermission()YesNo longer used after earlier deprecation removalsInternalUse Jira's API to check this Jira permissionOctober 2022

Java API

WorkAttributeValueService.getWorkAttributeValueById()

YesNo longer used after earlier deprecation removalsInternalUse other APIs within WorkAttributeValueService to retrieve the work attribute's value, e.g. getWorkAttributeValuesByWorklogOctober 2022

POST worklog attributes

/rest/tempo-rest/2.0/worklogs/{worklogId}/attributes

No

Better alternative, deprecated since Timesheets 8.0.0.

Update work attributes of a worklog

Update a worklog with its work attributes.

https://www.tempo.io/server-api-documentation/timesheets#operation/updateWorklog_1

October 2021

GET worklog attributes

/rest/tempo-core/1/work-attribute/value

Yes

It is not compatible with Tempo Team permissions.

Get all work attribute values of a worklog

Get a worklog and its work attributes.

https://www.tempo.io/server-api-documentation/timesheets#operation/getWorklog_1

October 2021

POST worklog attribute

/rest/tempo-core/1/work-attribute/value

Yes

It is not compatible with Tempo Team permissions.

Create a single work attribute for a worklog

Update a worklog and its work attributes. Work attributes can be partially updated.

https://www.tempo.io/server-api-documentation/timesheets#operation/updateWorklog_1

October 2021

GET single worklog attribute value

/rest/tempo-core/1/work-attribute/value/{id}

Yes

It is not compatible with Tempo Team permissions.

Get a single work attribute value by id

Get a worklog and its work attributes.

https://www.tempo.io/server-api-documentation/timesheets#operation/getWorklog_1

October 2021

PUT worklog attribute

/rest/tempo-core/1/work-attribute/value/{id}

Yes

It is not compatible with Tempo Team permissions.

Update a single work attribute value

Update a worklog and its work attributes. Work attributes can be partially updated.

https://www.tempo.io/server-api-documentation/timesheets#operation/updateWorklog_1

October 2021

DELETE worklog attribute

/rest/tempo-core/1/work-attribute/value/{id}

Yes

It is not compatible with Tempo Team permissions.

Delete a single work attribute value

Update a worklog and its work attributes. Work attributes can be partially updated.

https://www.tempo.io/server-api-documentation/timesheets#operation/updateWorklog_1

October 2021

POST user search

/rest/tempo-core/1/users/search

No

We need the endpoint to return deleted users as well and we no longer want to support searching by username (only by key).

Search for users

If any customer is using this private endpoint, they can switch to using the new endpoint that our own frontend uses as well:

/rest/tempo-core/1/users/searchByKey

October 2021