I'm at a loss as to why the Date Started on the work log is populated with the current date time. Shouldn't this be a Date Ended field instead, and populate with the current time?
In general no one I know can accurately predict to the minute how much time they WILL spend working on an issue and input that before they actually start working. The typical workflow is to start working an issue, and then when you are done for that chunk of time(say 2.5 hours) you then log work on the ticket with an explanation of what you did. So you're done....open the ticket, enter time spent....2.5 hours....but....the "Date Started" is now. So that means to be at all accurate I have to manually adjust the date started back 2.5 hours (otherwise it looks like I've logged future time--current date/time + 2.5 hours).
If users don't accurately manually adjust time (painful) then all the reports are screwed up. This is particularly bad on tickets that fall at the end of the month that might take several hours (maybe a day or two) and get logged at the end of the day--then it looks like they were worked in the following month. Not good.
How do others deal with this? Is there script or something that can automatically adjust the date based on the log time entered, but only if the user wants the calculation done (since sometimes we may need to go back a few weeks on a ticket to enter a couple of hours worked if someone forgot to log time, so locking the field isn't an option, nor is always auto adjusting it back).
