Bug 132676 - I get warned that journal-recorded TODO's are currently filtered
Summary: I get warned that journal-recorded TODO's are currently filtered
Status: RESOLVED UNMAINTAINED
Alias: None
Product: korganizer
Classification: Applications
Component: todoview (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-08-20 08:10 UTC by min
Modified: 2017-01-07 22:22 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description min 2006-08-20 08:10:52 UTC
Version:            (using KDE KDE 3.5.2)
Installed from:    Ubuntu Packages

I make extensive use of KOrganiser's filters, indeed a very useful feature. I also have Kontact configured to record completed TODOs in journal entries.

Each time I apply a filter and mark a TODO as completed, I get told that it's journal entry is filtered and will not be displayed. I eventually deactivated that dialog, but now I'm not covered against entering new TODOS without assigning them to the proper category :)

I assume journals and todos are all implemented as calendar entries, and that's why this behavior occurs. But please don't let the implementation express itself in the user interface. Don't warn against filtered journal entries.
Comment 1 Reinhold Kainhofer 2006-11-02 19:25:06 UTC
Reassigning all KOrganizer bug reports and wishes to the newly created 
korganizer-devel mailing list.
Comment 2 Denis Kurz 2016-09-24 18:51:23 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 3 Denis Kurz 2017-01-07 22:22:40 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.