You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Can I put a trigger to stop one from logging hours in the past.
If so, how can one go about it.
Most people log "hours in the past", and need to, because they often finish a task and then log it later.
That said, yes, you don't want people going back and amending logs after you've started reporting off their logs and your processes say they need logs in at a reasonable time, so it's perfectly reasonable to ask for this.
I'd want to start by asking what your rule for "past dated" is?
As an example, my group finds weekly reporting useful, but monthly very important, so we "lock" the timesheets (Tempo allows us to do this) a few days after month end. Your rule could be very different - maybe every week, or possibly process driven - if an issue is "closed", you don't want logs to be added or edited. And so-on.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.