One of my users accidentally logged time back in 2003. I picked it up in a downstream system as this was processed through the API. I then looked into the period management screen and realised that the drop down starts in 2018. And there is no other option to close all periods before that.
I logged this with support a couple of weeks ago and was told
"Currently the oldest year for schedule is only available up to 2018, everything older than 2018 when user is trying to log time should get error message " Period is closed"
then reverted a few days later saying
"Unfortunately the Tempo Period Management is not able to manage those periods far back in time, however, what you are experiencing is a valid use case. We invite you to add an idea as a feature request in our new idea portal (https://ideas.tempo.io/ideas). "
The support ticket is https://tempo-io.atlassian.net/servicedesk/customer/portal/6/TCS-26480
It would be very useful if not critical to have the ability to stop time being logged before 2018. as stated in your colleague's original feedback this was expected system behaviour.
Nicholas Tsiroyiannis
| Tempo Products | Tempo Timesheets |
| Tempo Platform | Cloud |
We are also facing the same issue when user inadvertently book hours for past years (i.e. 2000, 2001) which was never part of the "Period Management" then it is an error to destination system where these hours flows since they can't be deleted even. Ideally, tempo must consider those very old years as closed and should not allow users to book under those years which are older than 1st period management year.
Attachments Open full size