Not currently, but we’ve been getting similar feedback a bit so far, so we’ll see the appetite for that going forward.
Its often easier to just put in the time if you know it offhand. The new feature is helpful when putting in a time entry for an earlier time and you want the time stamp to be correct.
Wait actually I see with the new feature it does NOT enter the correct time stamp on a time entry entered for a previous time/date - so what’s the point of choosing the date option there?? Its just to calculate your minutes for you…?
Hey Abe, it does properly log the start time in the labor log. I just checked and it’s working as intended there.
Doesnt work for me I just tested again just shows the timestamp of when the time entry was entered
Oh I see what your saying it adds in the labor log but the time stamp of the actual time entry is when the time entry was entered. Would be nice if it showed in the ticket “communications” when the time entry/notes were entered AND when the actual labor was done so this way a manager for example (or even another tech) can easily see when work was done and when it was entered and not have to jump to the labor log for that
Well that isn’t how that part would work. There are two different times to track here. One is for when you entered the comment, and that needs to appear in reverse chronological order. The other is recording the time the actual work was done, which is handled in the labor log.
It wouldn’t make sense if communications were happening on a ticket, and a newly entered comment fell behind those because an older date was used for when the work was performed.
Comments can still be in chronological order but you can also have a time stamp of when the work was done. This way when a manager/dispatcher is looking at the ticket they can easily see the that John entered his time at the end of the day but was at ABC client at 11 AM. Autotask has this for example and I’m sure other PSAs do to.