Bug 204220

Summary:	wish: ability to apply filter action to entire thread
Product:	[Frameworks and Libraries] Akonadi	Reporter:	Reuben Martin <reuben.m>
Component:	Mail Filter Agent	Assignee:	kdepim bugs <kdepim-bugs>
Status:	REOPENED ---
Severity:	wishlist	CC:	jtamate, luigi.toscano
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Gentoo Packages
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Reuben Martin 2009-08-18 00:03:06 UTC

Version:            (using KDE 4.2.4)
Compiler:          gcc 
OS:                Linux
Installed from:    Gentoo Packages

I subscribe to quite a few mailing lists, so my IMAP account can take a while to filter through the large about of email I get each day.

My filters sort mail according the the list they are in, but the filters have to act on each individual email. It would be a lot quicker if when creating a filter, there was an option to "Move entire thread to folder" so that a group of related emails could all be moved at once to speed the filtering along and skip the extra work required to check each individual email.

Comment 1 Jaime Torres 2010-01-14 12:50:26 UTC

This will allow a faster workflow with bug mails. To organize the mails in folders depending on the bug status moving the whole thread when a mail with the bug status change arrives to another folder automatically.

Comment 2 Myriam Schweingruber 2012-08-18 08:08:45 UTC

Thank you for your feature request. Kmail1 is currently unmaintained so we are closing all wishes. Please feel free to reopen a feature request for Kmail2 if it has not already been implemented.
Thank you for your understanding.

Comment 3 Luigi Toscano 2012-08-19 00:10:36 UTC

Instead of creating a new feature request, please confirm here if the wishlist is still valid for kmail2.

Comment 4 Jaime Torres 2012-08-19 10:20:33 UTC

Yes, it is valid. An option to move the entire thread where the mail is will be very helpful.

Comment 5 Justin Zobel 2021-03-09 05:47:04 UTC

Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.