Summary: | Wish: Filter - add possibility to mark message with user-defined flag(s) | ||
---|---|---|---|
Product: | [Unmaintained] kmail | Reporter: | grzesiekw <grzesiekw> |
Component: | filtering | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED DUPLICATE | ||
Severity: | wishlist | CC: | christophe |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Unspecified | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: |
Apply tag with RMB
Filter window |
Description
grzesiekw
2009-07-16 14:15:09 UTC
I'm not sure to understand, you're talking about the tags ? (family, business...) If so, I have no problem to assign a custom tag to a filter (filter actions/Add tag/<a tag>) or to filter emails depending on their tag (Match all/Message Tag/contains/<a tag>). (In reply to comment #1) > I'm not sure to understand, you're talking about the tags ? (family, > business...) > > If so, I have no problem to assign a custom tag to a filter (filter actions/Add > tag/<a tag>) or to filter emails depending on their tag (Match all/Message > Tag/contains/<a tag>). No, I'm talking about custom tags which could be created in "Appearance->Message Tags". Created attachment 35562 [details]
Apply tag with RMB
Then we're talking about the same thing.
That's already possible.
Created attachment 35563 [details]
Filter window
And it's possible to filter message containing a tag and/or to apply a defined tag.
(In reply to comment #4) > And it's possible to filter message containing a tag and/or to apply a defined > tag. I don't know what king of branding do you have, because I don't have something like "Add Tag" in "Filter Actions". I've double checked it on Fedora and Gentoo, KDE 4.2.4 and 4.2.96 (4.3 RC2). I can make a screenshot (if you wish). Ah, I get it. This was implemented after the feature and string freeze for KDE 4.3. That's why it is only in the development version. This will be available in KDE 4.4 (or before if Opensuse wants to implement it in their packages) *** This bug has been marked as a duplicate of bug 136555 *** |