Time tracking not handling hours that go over midnight
complete
A
Adam Coady
If I manually add in some time for work completed, where the work goes past midnight, the system changes it to negative hours.
So for example, I added some time yesterday starting at 7pm and ending after midnight at 12:45am. Whether I use the up/down arrows to increase the time, or enter it manually, as soon as it goes over midnight it decides the duration should be a negative value - even though at the same time, using the arrows, it has understood that we've gone from PM to AM and made that change itself.
Geoff Mina
complete
We have made a small tweak to automatically tick up to the next day if you move the time past midnight.
A
Adam Coady
Geoff this is great - thank you!
Geoff Mina
planned
Geoff Mina
closed
Component requires manually setting duration on manual entry across midnight.
Geoff Mina
You just need to set the duration of you want it to go over midnight.
A
Adam Coady
Geoff Mina just to confirm, this is the intended way to use this:
https://www.loom.com/share/18a73fb707714740a801dccd931791ae?sid=c02904df-90a1-434e-a0f9-7837f6ddd264
If it is able to recognise as you press the up/down arrows that you've gone from 11:45pm to 12:15am (which it does), isn't it the same thing to recognise that the 30 mins you just added to the clock was also 30 mins added to the duration - rather than a change to negative 18 hours of work?
Geoff Mina
Adam Coady that’s definitely a bit funky. We can probably fix the up arrow behavior to get it to tick over ton the next day.
A
Adam Coady
Geoff Mina Hehe, definitely not the end of the world, but having the up/down arrow do the same thing for the duration as it does for the time, I think will mean it does what a user anticipates 99% of the time, rather than give a negative value that doesn't work 100% of the time :)