Tempo Ideas

To be honest I'm not sure this idea will help in my situation for Planner, I'm wanting to report at a team level going forward but adding a leaving date to an employee only removes them if the reporting period doesn't include any dates they're available.

Seems like quite a flaw in reporting for Planner

This impacts Planner reporting also per
https://tempo-io.atlassian.net/servicedesk/customer/portal/6/TCS-31146

it makes the planner reporting looking forward at capacity almost useless from x date forward without being able to end date a workload for a specific team member as the Required hours and Planned % data is incorrect where someone is not available from x date.

Is there any update on this?

Would really be great to also have a column with the sum of all the overtime accumulated through the different months, without having to do it manually after the export.

This comment applies more to the 3 "merged" ideas attached to this idea. When we moved from monthly to weekly time reporting, tempo "reopened" all the previously submitted/approved timesheets. This caused a HUGE amount of confusion and I had to write code to resubmit/approve all time sheets back to the beginning of the year.

Thanks for the feedback!

We are currently looking into adding support for start and end dates of workload and holiday schemes which would allow for accurate historical reporting on worklog data. At the moment I do not have an ETA, but I'm updating the status of this idea to "likely to implement".

Cheers,

Hlynur Johnsen

Group Product Manager - Tempo for Jira