Bug 203524

Summary:	Marking Todo item as completed -> loses parent
Product:	[Applications] korganizer	Reporter:	Adrian von Bidder <avbidder+kde>
Component:	general	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED FIXED
Severity:	normal	CC:	smartins
Priority:	NOR
Version:	4.3
Target Milestone:	---
Platform:	Debian testing
OS:	Unspecified
Latest Commit:		Version Fixed In:

Description Adrian von Bidder 2009-08-12 10:07:38 UTC

Version:            (using KDE 4.3.0)
Installed from:    Debian testing/unstable Packages

Heyho!

Marking a sub-TODO item as completed moves it to the top level of my TODO hierarchy.  This obviously is quite annoying since it makes checking off items essentially unusable (I *could* move the items back into the hierarchy, but since I've got quite a few TODO items this is not practicable.)

Comment 1 Adrian von Bidder 2009-08-12 10:09:05 UTC

Oh, yes: Debian 4:4.3.0-1 kdepim packages, on std.ics storage via akonadi, akonadi Packages are at Debian package version 1.2.0-2

Comment 2 Adrian von Bidder 2009-08-12 10:14:56 UTC

Errrm.

Just noticed: this is a "hierarchical TODO items don't work at all."

Extremely annoying.

Existing TODO items are displayed correctly in the hierarchy, but I can't create new sub TODOs.

Funnily enough, they're displayed firstin the hierarchy (for 1/10 second) but then the display is immediately redrawn with the TODO item at top level.

Comment 3 Adrian von Bidder 2009-08-12 10:22:09 UTC

Ok, this is limited to the akonadi backend.  Switching to a plain std.ics as standard resource fixes this, so it's either an akonadi problem or a problem in korganizer's akonadi interface.

(I was fiddling around with the resources in the first place because korganizer recently started to come up with an empty calender after every KDE log-in.  The std.ics was there and contained all data, so I didn't lose data at first, but then importing that again opened the calendar in a "RAM only" mode: all new changes would be lost without warning.  So now I'm exporting to a different ics file every now and then.)

And sorry for the followup orgy...

Comment 4 Sergio Martins 2010-03-03 01:09:03 UTC

I fixed this in trunk a month ago.

I won't do a backport to 4.4 because the code is very different and I don't have time for more debugging + patching.

Please wait for 4.5