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
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
Time logging in Jira is used for time reporting to clients, contractors, and so on.
Presently, Jira users can modify their time logs in the past. Hence, they may log certain time, a report will be submitted based on these hours. Then the user can modify its hours in the past. Then a new report will present a different info. Such discrepancy disqualifies Jira and its plugins from being source of truth for time logs.
Our company has to present a daily report of hours to clients. Then at the end of month we present a monthly report. These two reports do not reconcile, because team members can log their time after a daily report was already sent.
Same issue with contractors: they log one time at the end of day and then they may modify their time by mistake and submit a monthly receipt for a different amount.
It is too easy to make a mistake and log time to a wrong date. And it is very hard to check time logs on a daily basis for many team members. So, hard to enforce the idea that time logs in the past should be avoided.
My suggestion: provide an option to prevent time log in the past. For example, lock time log that was submitted more than X hours ago.