Tag rounding misbehaving

bernimoses

WorkingHours version:
OS + version: Android 2.11.27
Device model: Samsung S22

Hi, i have three things i noticed with the tag rounding feature.

I am not sure if this is a bug or intended behaviour, but i can't get the app to calculate the "correct" working times in hours and minutes (ignoring the seconds). I tried setting the tag to "up to next minute", "to nearest minute" and "down to next minute" but every time some entries are calculated wrong. The global rounding setting is set to "Don't round". I made a screenshot for every setting i tried and marked the wrong calculated time:

If i calculate the times myself the times would be (from top to bottom):

09:44 - 12:42 = 2h 58m
17:58 - 19:13 = 1h 15m
13:07 - 17:16 = 4h 9m
10:39 - 12:24 = 1h 45m
13:19 - 17:57 = 4h 38m
09:59 - 12:38 = 2h 39m

My guess is that because i use the start work button (most of the time) seconds are saved internally which causes this rounding behaviour. But shouldn't "down to next minute" ignore seconds completely e.g. if 09:44:xx is saved internally with xx being the seconds i clicked the start work button the rounding should make 09:44:00 out of it, right?

If i open a tag and close or save it, it changes the rounding amount to another value. E.g. "minute" > "5 minutes" > "15 minutes" > "minute". I made a screen recording to show it:

The global rounding takes precedence over the tag rounding. Shouldn't it be the other way around to be able to overwrite it with a tag for a specific task or work unit?

Thank you very much for your time and this awesome app. 🙂

timo

bernimoses My guess is that because i use the start work button (most of the time) seconds are saved internally which causes this rounding behaviour

This is exactly right.

bernimoses But shouldn't "down to next minute" ignore seconds completely e.g. if 09:44:xx is saved internally with xx being the seconds i clicked the start work button the rounding should make 09:44:00 out of it, right?

No, the app rounds the duration between start and end, it doesn't round the start/end times.

bernimoses If i open a tag and close or save it, it changes the rounding amount to another value. E.g. "minute" > "5 minutes" > "15 minutes" > "minute". I made a screen recording to show it:

That's clearly a bug and I will fix this with the next update - thanks for pointing it out!

bernimoses The global rounding takes precedence over the tag rounding. Shouldn't it be the other way around to be able to overwrite it with a tag for a specific task or work unit?

It's not that one takes over precendence over the other, but both roundings are applied - first the global rounding and then the tag rounding

bernimoses Thank you very much for your time and this awesome app. 🙂

Thanks for your kind words 🙂

bernimoses

timo No, the app rounds the duration between start and end, it doesn't round the start/end times.

hmm ok, this explains it. It wasn't obvious to me and it doesn't help calculate the time correctly if you care about the time between start and end. Is there another way to get the correct time?

timo That's clearly a bug and I will fix this with the next update - thanks for pointing it out!

Thank you.

timo It's not that one takes over precendence over the other, but both roundings are applied - first the global rounding and then the tag rounding

oh, ok i feel like this is kind of unintuitive. would be nice to get at least a info/warning notice somewhere.

timo

bernimoses hmm ok, this explains it. It wasn't obvious to me and it doesn't help calculate the time correctly if you care about the time between start and end. Is there another way to get the correct time?

What do you mean with "the correct time"? Why is the current behavior incorrect?
You can manually adjust the start/end times, which will cause the seconds of the start/end times to be discarded

bernimoses

With "correct" time i mean: I can only see/edit hours and minutes and if i calculate e.g. 17:58 - 19:13 it should be 1h 15m and not 1h 16m or 1h 17m depending on the hidden seconds. And because of how the rounding works there is no way to always (in every case) get this "correct" time. It all depends on the hidden seconds. I am not complaining about how the rounding is working, that is a design decision and i understand if you don't want to change it or even break it for other people. But at least for me it wasn't intuitive and the app doesn't tell me how it works (maybe an improvement, like a notice e.g. a info icon next to the rounding feature that explains it in a sentences, would be good?).

It would be nice to have another option for rounding the start/end times or something else that allows me and potentially others to get the times calculated as i would expect it if is see e.g. 17:58 - 19:13. Editing every entry to be sure there are no seconds saved seems like more like a workaround and less like a solution.

A potential use case would be:
If i charge a customer for every started quarter hour (15 minutes) and i start my work at 13:17 and work until 13:39 which would translate to started work at 13:15 and finished it at 13:45 resulting in 30m charged. Currently round to nearest 15m and down to next 15m would give me only 15m. If i change it to round to next 15m it would give me the the 30m. But then if i work from 13:17 to 13:32 it would only give me 15m again even though the work started between 13:15 and 13:30 and ended between 13:30 and 13:45 which would be 30m. If there would be an option to round the start down to the next 15m and the end up to next 15m the desired time of 30m (13:15 - 13:45) would work.

I think i found a feature request that seems like something similar was already requested a few years back. But i am unsure if the above use case would be covered by this. If it does it would be awesome to see this implemented. 🙂

timo

Thanks doe the additional details and the use-case.
Yes I believe that linked feature request desribes what you want - thanks for commenting under it as well. But I don't plan to add it in the near-term - sorry.