For reporting reasons it would be great to get access to the historical data on workload assignments (secure/Tempo.jspa#/settings/workloads). At the moment only the currently assigned workload-scheme is visible, we'd like know when an employee changed from 80% to 100% to 30%, i.e. during partial paternal leaves or the like. Are there any plans to extend this similar to team-assignments (i.e. date-based)?
Guest
| Tempo Products | Tempo Timesheets |
| Tempo Platform | On-Premise |
0
Likely to implement
0
Likely to implement
0
Likely to implement
Is this something that can be built for the Cloud version?
For us this is really an important functionality for the Review Reporting (e.g. look back and find out about how many projects whre overbooked based on the settings at that time.
What happened to the implementation of the idea?
Currently there is no start-/end date for workload configurations.
Best regards,.
Benny Nestler
its exactly the same. We are working with working students and freelancers and the capacity differs from time to time (e.g. working students normally work 20h / weeek, during semester break they can work up to 40h/ week or with freelancer they sometimes work 16h/ week and in project peaks they support us up to 40h/ week). It would be great to get that update !
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