Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Stopping past dated logging work

Can I put a trigger to stop one from logging hours in the past. 


If so, how can one go about it. 

1 answer

0 votes
Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Feb 25, 2021

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.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events