This article is for Timesheets for Cloud. Visit Data Center

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 54 Next »

We welcome all feedback via our Slack channel: tempo-labs.slack.com.

Tempo is currently offering and/or developing the following release candidates for its TempoLab customers. Customers should be aware that once the Tempo Admin enables the TempoLab in their instance, all features listed below will be available to them.

Feature

Date available

Testing ends

Release notes

Alternative method for syncing Tempo worklogs with Jira

Early August 2024

September 2024

In preparation for the upcoming Atlassian worklog limit per Jira issue, we’re introducing a method to reduce the number of worklogs that are added to a Jira issue. By default, when you create a Tempo worklog, a corresponding Jira worklog is also created. You can now choose to create an aggregated Jira worklog for all Tempo worklogs created for an issue per day.

Override closed periods or approved timesheets

Late August 2024

September 2024

In preparation for the upcoming Atlassian worklog limit per Jira issue, we’re introducing a method to reduce the number of worklogs on existing Jira issues.

Using Override Mode you can move or delete worklogs from closed periods or approved timesheets. This override applies to the Tempo App and Tempo APIs.

  • No labels