I used KTimeTracker for logging my job history. Each work day has approximately 8 - 9 hours. I've divived records by year, then by months, then by days and finally by job tasks. Now, I've more days over 10 hours, for example one day has 70h, next 38, next 31 etc... Reproducible: Always
Version 4.14.3
Created attachment 91260 [details] Detailed printscreen of incorrect times
I can confirm this happening to me. In my case, it happened after a distro upgrade (Mageia 4 to Mageia 5), thus going from ktimetracker 4.12.5 to 4.14.5. New tasks seem to be working properly (so far), but old ones are all messed up. Exporting provides the same wrong result, but if i go to history edit mode and manually sum times, the result is what i expected. This is only a hunch, but i think it's related to tasks and subtasks having both time spent on them.
Hello! Sorry to be the bearer of bad news, but this project has been unmaintained for many years so I will be closing this bug.
(In reply to Carlos Vives from comment #3) > I can confirm this happening to me. In my case, it happened after a distro > upgrade (Mageia 4 to Mageia 5), thus going from ktimetracker 4.12.5 to > 4.14.5. > New tasks seem to be working properly (so far), but old ones are all messed > up. Exporting provides the same wrong result, but if i go to history edit > mode and manually sum times, the result is what i expected. > This is only a hunch, but i think it's related to tasks and subtasks having > both time spent on them. I need an example .ics save file that gives different totals - in tasks table/export and - in history dialog, in order to understand where the issue comes from and to test against the new Qt5/KF5-based version of KTimeTracker.
Still need an example .ics file from ktimetracker 4.12.x to test against newer versions.
I don't know about the original opener of the bug, but i stopped using ktimetracker in 2018 due to the lack of maintaining and lack of confidence in totals produced. I don't think i keep copies of the flawed ics.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!