Skip to main content
Skip table of contents

Tempo Cloud Releases

2024-12-02

Reporting

Sharing Financial Manager Projects

  • When sharing projects with other team members, you can restrict them to specific individuals or make them available to all users who can access projects. The open access option has been renamed from Users with App Access to Users with Tempo Projects Access.

    new-access.png

2024-11-27

Sync aggregated worklogs on Internal Issues to Jira

2024-11-26

Tempo Global Permissions - Granular Financial Manager Permissions

  • You can now provide more granular access control for Financial Manager. The permissions have been separated into the following:

    • Tempo Project Administrator - create, view, manage, delete all projects and modify global project settings.

    • Tempo Project Manager (previously Financial Manager Access) - view, create, delete, and manage projects they own and approve project time. They can edit projects other team members own when granted the Editor role in the project.

    • Tempo Project Viewer - view projects that they’ve been granted access to and approve time in those projects.

  • If you already have Financial Manager installed, you may want to review the global permissions granted to your users, due to the privilege and enrolment changes in the permissions.

    • Existing users with app access are granted the Tempo Project Manager permission by default.

    • Jira administrators are granted the Tempo Project Administrator and Tempo Project Manager permissions by default.

    • Tempo Administrators require the Tempo Project Administrator permission to access Settings > Tempo Projects.

    • Tempo Project Managers can no longer edit global project settings.

  • For more information about Financial Manager permissions, view the documentation.

2024-11-15

Validate account when moving worklogs between issues

  • A new option has been added to the Logging Time settings screen: Users can move worklogs when accounts are not linked to the destination project.

    2024-11-15_11-48-46.png
  • This is enabled by default, allowing users to move worklogs from one issue to another, even if the new issue is in a project not linked to the current account.

  • Administrators can disable this feature to require users to select a new account if they try to move a worklog (or multiple worklogs) to a project not linked to the current account.

2024-11-14

Centralized view for team- and project-level approvals

  • Both timesheet and project approvals are now available in My Work under the Approvals tab. This centralizes project and team-level approvals, enabling Project and Team Leads to efficiently approve hours for multiple users across various teams and projects in a single location. Project approvals are only available when Financial Manager is installed with Project Time Approval enabled. 

  • When you view the periods, you can view both your timesheet and any project time logged for the period. 

  • The Approval Log also shows both timesheets and project time. 

  • If there are project approvals associated to a timesheet, Team Leads can get an overview by clicking on View project approvals. 

  • You can still approve project time from the Project Approvals tab.

New Rejected status

  • Rejected timesheets are now indicated by a Rejected status in these parts of the UI: 

    • the new Approvals view 

    • the Team Approvals view

    • the Approval Log 

    • the timesheet submission form

  • Please note that the Rejected status is only available in the UI; exports and APIs will continue to return the old values for rejected timesheets (either Open or Ready to Submit). 

Backup approvers for project time

  • You can add backup approvers for projects in your project's configuration. The default approver is notified when project time needs to be approved, but any approver can approve or reject project time from the Approvals tab in either their project or in My Work. Approvers must have the Viewer role in the project.

Updated Labor Cost CSV

  • The Labor Cost CSV export now has the Project Approval Status column. 

Other improvements

  • Fixed: The action button loaded indefinitely when viewing a rejected timesheet through Team Approvals.

2024-11-13

  • Fixed: Occasionally, some holidays were not returned in the listing.

2024-11-08

  • Fixed: In rare instances, Tempo synchronized the same worklog twice with Jira, resulting in two Jira worklogs for the same Tempo worklog.

  • Fixed: Can’t resubmit your own timesheet if the status is Rejected.

2024-11-07

  • Fixed: Could not install integrations from the Tempo Apps in Safari.

2024-10-28

Update to Rejected Plans in Planned Time and Planned vs Actual Reports

  • When generating a Planned Time or Planned vs Actual report, rejected plans are now filtered out by default. Previously, rejected plans were automatically included in these reports.

  • To include rejected plans in your future reports, you can now choose a filter called Approval Status and then select the Include rejected plans check box. You can choose this filter when you create a report and also when you view a report. 

  • For more information, visit: Filtering the Data in Reports, Planned Time Reports, and Planned vs Actual Reports.

2024-10-17

Override Closed Periods or Approved Timesheets

  • 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.

2024-10-11

Reporting

  • Grouping by Tempo Team now uses the Tempo Team assigned to the Jira issue when grouping time records, worklogs, or plans. If present, this team is prioritized over the team the user last joined. Previously, only the information from the last team they joined was used when you grouped a report by Team or Role.

2024-09-18

Tempo Global Permissions - Changes to Tempo Financial Manager permissions

  • The Tempo Financial Manager Access global permission has been renamed to Tempo Project Manager. This change only impacts the permission's name and does not affect any current users or groups who are granted it. No other changes to the permission have been made, and you should continue to use this to grant your users access to Tempo Financial Manager.

  • Added two new permissions that are currently inactive:

    • Tempo Project Administrator - By default, Jira Administrators are granted this permission. This will allow users to manage all projects, including global project settings.

    • Tempo Project Viewer - This will allow a user to have limited access to projects that have been shared with them.

2024-09-16

  • Fixed: The Remaining Estimate in the Tempo Sidebar in the Jira issue view was not always up-to-date with Jira's own Remaining Estimate value.

2024-09-04

Timesheets and Portfolio Manager Integration

  • If you leverage Portfolio Manager for capacity planning, schedule forecasting, and scenario modeling in your Jira projects, you can now pull Timesheets worklog data into Portfolio Manager

  • Portfolio Manager uses Timesheets worklogs to provide up-to-date reports and forecasts, with time tracking automatically adjusting remaining estimates that are then used for schedule forecasting.

2024-09-02

  • Fixed: A permission check error was displayed when generating the Labor Costs CSV export.

2024-08-29

  • Fixed: Timesheet approval comments were cut off inside the column.

2024-08-27

  • Fixed: You couldn’t bulk add members with & in the group name.

2024-08-23

  • Fixed: The Basic calendar mode in My Work only displayed up to 250 calendar events per week.

2024-08-21

Reporting

  • You can now group by a checkbox type Jira custom field. The first value returned by the Jira API is used to group the data.

Other improvements

  • Fixed: When you created a multi-period plan, the Capacity report didn’t display the planned time correctly.

  • Fixed: When a plan extended into the next period, the planned hours in the Capacity report and Planned Time report didn’t match.

2024-08-16

  • Fixed: Couldn’t open a user's timesheet in a new tab in approvals.

2024-08-15

Reporting - Raw data export changes

  • The following changes have been made to the Logged Time Report raw data export, which impacts people who use column order, index number, or column name to fetch data. These changes help address reporting accuracy, especially when rounding from seconds to hours.

    • Hours has been renamed to Logged Hours.

    • Billed Hours has been renamed to Billable Hours.

    • Issue Original Estimate has been renamed to Issue Original Estimate Hours.

    • Issue Remaining Estimate has been renamed to Issue Remaining Estimate Hours.

    • A new column, Logged Seconds, has been added adjacent to the Logged Hours/Hours column.

    • A new column, Billable Seconds, has been added adjacent to the Billable Hours/
      Billed Hours column.

    • A new column, Issue Original Estimate Seconds, has been added adjacent to the Issue Original Estimate/Issue Remaining Estimate Hours column.

    • A new column, Issue Remaining Estimate Seconds, has been added adjacent to the Issue Remaining Estimate/Issue Remaining Estimate Hours column.

    If you download your raw report data to Excel, the following changes also occur in the Logged Time Report’s Users tab.

    • Worked has been renamed to Logged Hours.

    • Billed has been renamed to Billable Hours.

    • Planned has been renamed to Planned Hours.

    • Required has been renamed to Required Hours.

    • A new column, Logged Seconds, has been added adjacent to the Worked/Logged Hours column.

    • A new column, Billable Seconds, has been added adjacent to the Billed/Billable Hours column.

    • A new column, Planned Seconds, has been added adjacent to the Planned/Planned Hours column.

    • A new column, Required Seconds, has been added adjacent to the Required/Required Hours column.

2024-08-01

  • Fixed: In some cases, the group by option was incorrect in Mozilla Firefox.


Previous Release Notes

JavaScript errors detected

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

If this problem persists, please contact our support.