We have this longstanding client side js issue with the time not being correctly set, either on the 'start time', when creating a new timesheet entry or the 'end time' when 'now' is clicked.
ie. when clicking now on end time, the time remained 11:45 instead of 11:01.
It happend multiple times the other day, when the dates crossed over 11-12.
See screenshot.
I'm not sure if this info will lead directly to the issue, or a reproducible test case, but at least it's evidence.
http://i45.tinypic.com/1z1wp69.png
We have this longstanding client side js issue with the time not being correctly set, either on the 'start time', when creating a new timesheet entry or the 'end time' when 'now' is clicked.
ie. when clicking now on end time, the time remained 11:45 instead of 11:01.
It happend multiple times the other day, when the dates crossed over 11-12.
See screenshot.
I'm not sure if this info will lead directly to the issue, or a reproducible test case, but at least it's evidence.
http://i45.tinypic.com/1z1wp69.png