Expand my Community achievements bar.

Do you have questions about the migration to Adobe Business Platform? Come join our upcoming coffee break and ask away!

Backdating Time

Avatar

Level 10
Hello Everyone, Is there a way to prevent people from backdating hours (i.e. logging hours in a task/issue/project for 2 months ago)? I know we can prevent logging hours on completed tasks/issues. But what if it's still open, or I suppose they can still open it, log time, and close it again. Hope you are all well. Looking forward to Leap. Vic Alejandro PMP, CSM Denver Board of Water Commissioners
12 Replies

Avatar

Level 10
A taser might do the trick, Vic, but I'd suggest you check with the local sheriff before you go that route. (so...that'd be a "no", as far as I know) Regards, Doug Doug Den Hoed - AtAppStore SEE you at LEAP using the GPS App! https://tinyurl.com/LEAPGPS Got Skills? Lend a hand! https://community.workfront.com/participate/unanswered-threads

Avatar

Level 10
We found that turning on timesheet approvals is the best way to stop that practice. We are hyper vigilant that all timesheets are submitted and approved weekly. If someone needs to go back in time they request an admin to open that timesheet up and we reply once we do to include their manager. The timesheet gets approved again by their manager. Hope that helps.

Avatar

Level 2
We control how many time sheets users can see and we "close" them once the time sheets are submitted. Try that, because our users can't even see time sheets after they're submitted. Deb Hapka Thomson Reuters - Corporate

Avatar

Level 10
One more vote for timesheet approvals as the solution :) David Cornwell

Avatar

Level 2
Greetings, how do you prevent someone from logging time to closed issues/tasks? I'm finding that the only way I can do that is by closing out the project? Stacy Gandza RAPID RTC

Avatar

Level 4
Stacy, If you change the people's permissions to the task to view they won't be able to log time. I have not tested what happens when the task is pinned on their timesheet but I am assuming they won't have access to the task on their Timesheet as well. Make sure that when you mark it as complete you unshare it or give them view rights only. Please let me know if this helps!! Thanks, David
DAVID A. TAYLOR Founder & Managing Consultant

Avatar

Level 2
Thanks - I don't know how to "unshare" the task.... can you be more specific? The people have "inherited" permissions to the task through the Project settings. And they still need access to the project to see and charge time to the other tasks. I couldn't locate where to change the access to "view" on a task basis. Thanks again! Stacy Gandza RAPID RTC

Avatar

Level 4
Stacy, When in the task, go to task actions in the upper right hand corner, and click on sharing. Click the x next to inherited permissions to take away those inherited permissions to just that task. This will not affect their access to the project or other tasks. Then, if you want, you can then share it again with individuals or a team and make their access view only. Let me know if you would like to do a screen share to walk through it. Thanks! David
DAVID A. TAYLOR Founder & Managing Consultant

Avatar

Level 2
Thanks, this is helpful! :) Stacy Gandza RAPID RTC

Avatar

Level 10
Hi Vic, Scrolling up on this one, I see that I said "no", originally...but I had another idea. Our "http://store.atappstore.com/product/ubercalc/">UberCalc solution could police any time entries and "zero out" (with an explanation) any time entered on a Task that has been closed for a certain amount of time (e.g. after 7 days, to allow for some graceperiod; whatever cadence makes sense for a particular Workfront client's domain) effectively Brute Forcing the concept of no backdating of time. Regards, Doug Doug Den Hoed - AtAppStore Got Skills? Lend a hand! https://community.workfront.com/participate/unanswered-threads

Avatar

Level 10
Thanks Doug. Funny you went back in time (April) to answer this Backdating Time question �� . We ended up making a code change to our Integration API (which passes hours to JDE) to ignore any hours that have been entered for a date that's older than 1 month. We track our actuals in JDE. So we kind of corrected it on the backend.

Avatar

Level 10
Hah! Funny indeed, Vic; nice observation. And once again, you and I are Great Minds Often... / Fools Seldom... History will tell. Either way, "denying" back dating is the punchline, whomever tells the joke. For those reading who are not yet as advanced with the API as Vic and his team, I'd be happy to provide more information on how UberCalc solution solves this one; just drop me a line at doug.denhoed@atappstore.com. Regards, Doug Doug Den Hoed - AtAppStore Got Skills? Lend a hand! https://community.workfront.com/participate/unanswered-threads