-
Notifications
You must be signed in to change notification settings - Fork 17
Monthly summary miscalculation #66
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Labels
Comments
Hey, thanks for reporting. Can you check which application version you are using by going to settings and about. The version number and build number should be visible there. |
1.3.7-1
/P
Olavi Haapala kirjoitti sunnuntai 1. huhtikuuta 2018:
… Hey, thanks for reporting. Can you check which application version you are using by going to settings and about. The version number and build number should be visible there.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or mute the thread.
--
Lähetetty Jollastani
|
Ok. Thanks. That's the newest version. I'll have to take a look at what's wrong. |
I can give last month numbers if it helps?
Pekka
Olavi Haapala kirjoitti maanantai 2. huhtikuuta 2018:
… Ok. Thanks. That's the newest version.
I'll have to take a look at what's wrong.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or mute the thread.
--
Lähetetty Jollastani
|
Closing this as this should not happen anymore after the recent (LOL, ~2Y ago) refactorings |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
got 150:60.. isn't that just about 151h?
The text was updated successfully, but these errors were encountered: