Bug 186067

Summary:	"Mark thread as important" no longer expands thread
Product:	[Unmaintained] kmail	Reporter:	adam.hawthorne
Component:	new message list	Assignee:	Szymon Stefanek <pragma>
Status:	RESOLVED UNMAINTAINED
Severity:	normal
Priority:	NOR
Version:	1.11.90
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description adam.hawthorne 2009-03-03 20:38:12 UTC

Version:           unknown (using 4.2.00 (KDE 4.2.0), Kubuntu packages)
Compiler:          cc
OS:                Linux (i686) release 2.6.27-12-generic

Threads previously marked as important are normally expanded automatically in the message list.  In the new message list window, marking a thread as important (I have this set to a shortcut key) used to immediately expand the current thread, and now it doesn't.

I know about the other shortcut keys to expand/collapse a thread, but since "important" messages are supposed to be open, this is a behavior regression.

Comment 1 Jaime Torres 2009-03-07 13:11:33 UTC

In kmail 1.11.90 using Versión 4.2.65 (KDE 4.2.65 (KDE 4.3 >= 20090226)) "release 1.5", it is possible to configure the way the threading works, including which threads will be always expanded.
If you mark a thread as important, it is not expanded immediately, but if you visit another folder and comes back, it will be expanded.

Comment 2 adam.hawthorne 2009-03-07 20:24:27 UTC

This is also the case in KMail 1.11.0 , but the goal is to have particular threads expanded automatically.  By expanding an important thread immediately, the goal is met as soon as possible.  Why require the additional two steps of changing away from the folder and then changing back in order to cause the thread to become expanded, if the user has already stated he wants those threads expanded automatically?

Comment 3 Laurent Montel 2015-04-12 09:41:33 UTC

Thank you for taking the time to file a bug report.

KMail2 was released in 2011, and the entire code base went through significant changes. We are currently in the process of porting to Qt5 and KF5. It is unlikely that these bugs are still valid in KMail2.

We welcome you to try out KMail 2 with the KDE 4.14 release and give your feedback.