Bug 207414

Summary: Korganizer Journal wrongly adds completed to-dos to last recorded entry
Product: [Applications] korganizer Reporter: homoludens <homoludens1000>
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED UNMAINTAINED    
Severity: normal    
Priority: NOR    
Version: 4.3   
Target Milestone: ---   
Platform: openSUSE   
OS: Unspecified   
Latest Commit: Version Fixed In:

Description homoludens 2009-09-15 07:03:26 UTC 
Version:            (using KDE 4.3.1)
Installed from:    SuSE RPMs

Kontact / KOrganizer's Journal function has come a long way and is very useful now. The ability to have 'completed to-do's recorded in Journal entries' (Configure Kontact > Calendar > Views > To-do view > Other options), for example, is one of its great features.

Kontact records completed to-dos in the last Journal entry of that day, but this creates problems if the entry doesn't relate to 'completed to-dos' and should be changed. (If no entry for that day exists, however, Kontact will create an entry 'Journal of <date>' and record the to-do there.)

EXAMPLE:
Say I wrote a Journal note on a completed meeting with the head of GM regarding our takeover offer, I don't want to see at the bottom an entry "Completed to-do: Buy Bananas", which I did later that day.)

EXPECTED BEHAVIOR:
Kontact / Journal should always create a new entry for recording completed to-dos, ideally not simply entitled "Journal of <date>", but "Completed to-dos".
If such an entry already existed, it would be great if Kontact could append new entries to this entry, in order to keep records of all the completed to-dos for that day in one place.
Comment 1 Denis Kurz 2016-09-24 18:53:07 UTC 
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of korganizer (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.
Comment 2 Denis Kurz 2017-01-07 22:15:31 UTC 
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.