Bug 235629

Summary:	editing task times reverts other task times to zero after 4.4 upgrade
Product:	[Applications] ktimetracker	Reporter:	jamese <james.ellis>
Component:	general	Assignee:	Thorsten Staerk <dev>
Status:	REOPENED ---
Severity:	normal	CC:	agnez.flugunfaehiger.seevogel, 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 jamese 2010-04-28 14:55:27 UTC

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

Hi

I recently updated ktimetracker to 4.4 along with a KDE update. Notwithstanding the other bugs raised due to this update, I've just noticed another issue which is that some task times have reverted to zero.

Here is an example:

before (from a backup - not opened in ktimetracker) :

BEGIN:VTODO
DTSTAMP:20090424T135931Z
X-KDE-kontact-totalSessionTime:45
X-KDE-kontact-totalTaskTime:45
CREATED:20090417T051233Z
UID:libkcal-352961322.686
LAST-MODIFIED:20090424T135931Z
SUMMARY:xxx
RELATED-TO:libkcal-245479754.425
PERCENT-COMPLETE:0
END:VTODO


after (current file, opened in ktimetracker):

BEGIN:VTODO
DTSTAMP:20100428T121944Z
X-KDE-kontact-totalSessionTime:0
X-KDE-kontact-totalTaskTime:0
CREATED:20090417T051233Z
UID:libkcal-352961322.686
LAST-MODIFIED:20100428T121944Z
SUMMARY:xxx
RELATED-TO:libkcal-245479754.425
PERCENT-COMPLETE:0
END:VTODO


I haven't manually updated any tasks to be zero times, especially those listed back in 2009 (this is just an example out of a whole lot of examples). The only commonality I can see across all the tasks that have reverted to zero is that the times were edited manually rather than by using the start/stop timer (e.g edit task, add 45 minutes).
For instance, if this task had a zero 'timed' duration and 45 minutes added manually then ktimetracker 4.4 has somehow decided that only the timed duration counts towards the task time.

I'm wondering how task times can revert to zero and whether my task times can be rescued somehow? I really need them to bill clients accurately ... !


Thanks for any help. J

System: Kubuntu 9.10, KDE 4.4.2 up to date packages.

Comment 1 jamese 2010-04-28 15:13:41 UTC

ok, just did some more digging on this.

I opened a copy of the file from backup into ktimetracker and the task in question was visible at 45 minutes duration. I checked the ics file and could see the same. I closed the file, reopened it and the 45 minute task was visible still. All good.
I then Edited the task after it using "Edit Times" and added a minute to the start time. Clicked out of the field in the Comment field, there was a pause and random tasks in the calendar were updated with zero times and some were updated with very long times (like one task in one week was altered to 92hrs - longer than the working week!), including the one in question.

Looks like the bug resides in Edit Times. Hopefully it can be duplicated. Until it's fixed I can't use Ktimetracker if it's going to behave like this and corrupt the source files.

Thanks, J

Comment 2 jamese 2010-04-28 15:15:45 UTC

altering subject to match the previous comment

Comment 3 jamese 2010-06-04 05:12:46 UTC

Is there actually any point in lodging bugs about ktimetracker? 

I have times stored in ics files that ktimetracker that ktimetracker has either altered, modified or set to zero.

The maintainer doesn't seem to be interested in looking at or triaging bugs for this application. If the maintainer doesn't have the time or resources to work on KTT then maybe it should be passed off to someone else or work split up between more people.

I have clients who need task times and I've ended up having to send them screenshots of KTT task lists. I reference this bug as the cause as well.
Why? because I can't edit times in KTT without it completely screwing up historical times throughout the ICS, I then have to save times next to the title of the task, and manually add it up. To cap it all off, KTT doesn't export tasks to the clipboard with zero times -> resulting in a screenshot being the best way to save a task time.

Don't even attempt to use KTT via Kontact either as the wait time for loading files, editing tasks and adding new ones is phenomonal.

What a a load of rubbish, I've had enough.

Comment 4 agnez 2010-06-09 20:09:18 UTC

same problem here, working with data from a former version is a catastrophe. Hope this can be figured..