The approval process of timesheets along with required hours and notifications does not support the joining date of staff members in their teams. We should only consider the effective dates of team membership for the required hours to log in a period.
Ingi Brown
| Tempo Products | Tempo Timesheets |
| Tempo Platform | Cloud |
2
Future consideration
4
Future consideration
Isn't this actually a bug? Why do we enter the joining date if not for proper calculation of expected hours?
Hi, this "feature" would be really useful. Having only one resource that doesn't contribute to the system for the entire period would distort both their individual metrics and their team's average.
We have based our Flex time (over- under time) based on the Tempo data and when a new employee start during the month then this messes the calculation up. So if we could just have a start date for a Tempo user then this would be very beneficial.
This would be a really helpful piece of functionality for us
Any progress with this idea? The current behaviour of required hours is very confusing and affects time tracking controls and the approval process.
There are also duplicates:
https://ideas.tempo.io/ideas/T-I-83
https://ideas.tempo.io/ideas/T-I-519
This is really a big thing for us and a potential blocker as it screws up reports
As I remember those functionality was al ready in old Tempo