Bug 237367

Summary:	Task that was active when closing the app is active again when starting it
Product:	[Applications] ktimetracker	Reporter:	Oliver Klee <dev+kde>
Component:	general	Assignee:	Zoltan Gyarmati <mr.zoltan.gyarmati>
Status:	REOPENED ---
Severity:	normal	CC:	aspotashev
Priority:	NOR
Version First Reported In:	4.6.x
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Oliver Klee 2010-05-12 11:51:11 UTC

Version:           4.4.2 (using KDE 4.4.2)
OS:                Linux
Installed from:    Ubuntu Packages

Steps to reproduce:

1. start ktimetracker
2. create and start a task
3. decide to call it a day and log out of KDE (and maybe power off the computer)
4. at another day, log in to KDE again, and do some other work
5. after an hour or two of work, open ktimetracker

Expected result:
ktimetracker is automatically started with KDE, but no task is running.

Actual results:
ktimetracker is automatically started with KDE, and the task that was running when you logged out has been running for another hour (the time since the login), ruining the time tracking data (because you have been working on something different).

This is a usability issue (because the application does not behave in a way that a user would expect in a typical usage scenario) and a potential data loss issue with effects on billing (because the time tracking data become unusable if time gets recorded that has nothing to do with the task).

Comment 1 Thorsten Staerk 2010-05-14 19:39:21 UTC

I think I designed it like this for KDE 4.3 and 4.4, but reverted the decision because of negative user feedback with KDE 4.5. Can look it up in June.

Comment 2 cristi.posoiu 2011-03-26 12:13:58 UTC

Taking aside this is not working always correctly (resuming tasks), I understand there are different opinions about this.
So, I would suggest adding a preference like 'Auto restart running tasks when loading data" - boolean, and use it in taskview.cpp:load to skip over the part that tries to resume the tasks.

Comment 3 Thorsten Staerk 2011-09-29 11:25:16 UTC

I do not want to control this via options, I don't want to double my work. The report is valid. If you restart ktimetracker (quit and start it again), the task will no longer be running. But if you - as this bug report describes - log out, the task will not be stopped and will continue to run.

CONFIRMING this bug.

Comment 4 Thorsten Staerk 2011-09-29 11:47:30 UTC

And here is the problem - stopping a task is nothing more than adding an end date to it. If you break ktimetracker (instead of quitting it) there is no end date. This is why we show the task as running - every second that passes adds a second to the task's time.

Comment 5 Andrew Crouthamel 2018-09-04 18:53:26 UTC

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.