Bug 78416 - mark thread as important unmarks when it should mark
Summary: mark thread as important unmarks when it should mark
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail
Classification: Applications
Component: general (show other bugs)
Version: SVN trunk (KDE 4)
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2004-03-24 23:40 UTC by arutha
Modified: 2015-04-12 10:25 UTC (History)
2 users (show)

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 arutha 2004-03-24 23:40:27 UTC
Version:           1.6.1 (using KDE 3.2.1, Gentoo)
Compiler:          gcc version 2.95.3 20010315 (release)
OS:          Linux (i686) release 2.6.3

When a thread is already marked as important and some new messages arrive KMail does not behave as expected. The new messages are _not_ marked as important. Ok I can live with that, but when trying to mark the rest of the thread as important (by choosing Mark Thread->Mark thread as important on a message that is not yet marked important) all previously marked messages in the thread get their mark remove instead of the new ones getting the mark set.

This behaviour would be ok for an already marked message where you clearly see that the option is toggled on, but the new messages all have their 'mark as important' toggled off.
Comment 1 arutha 2004-05-10 19:01:25 UTC
Still happens with KDE 3.2.2.
Comment 2 Andreas Gungl 2005-06-12 20:32:52 UTC
Works fine at least in KMail 1.8.1 (KDE 3.4).
Comment 3 arutha 2005-06-13 23:19:14 UTC
Not really. If the first message in a thread is marked and you select "mark thread important" on another message in the thread, the mark gets removed from the first message. Result: No marked messages in thread.

If some message under the root is already marked important and some message is selected and the "mark thread important" action is invoked, the thread is correctly marked important as a whole.

Problem: In most cases the first message in a thread is already marked as important.
Comment 4 Andreas Gungl 2005-06-14 08:48:19 UTC
Ah, I see. Confirmed.
Comment 5 Shriramana Sharma 2005-11-25 09:44:11 UTC
I was going to file this as a separate bug, but decided to add comments to this bug which is very similar to my bug -

Title I was going to give to my bug:
Hitting "mark as not to-do" marks messages as to-do - special case

Am using KDE 3.5RC1 level "a" on SUSE Linux 10.0. KMail version is 1.9.

How to reproduce the bug:
1. I have a message marked to-do in a folder.
2. I click on it.
3. I hit Ctrl+A using the keyboard so all messages in that folder are selected.
4. I right-click on the message marked to-do.
5. I click on the option "Mark as not to-do".

Actual result:
All the messages in the folder are marked *to-do* and NOT *not to-do*.

Expected result:
All the messages in the folder are marked *not to-do*.

Observed behaviour related to the bug:
1. I have a message marked to-do in a folder.
2. I click on another messaged NOT marked to-do in that folder.
3. I hit Ctrl+A using the keyboard so all messages in that folder are selected.
4. I right-click on the message NOT marked to-do.
5. I click on the option "Mark as to-do".
Result: All the messages in that folder are marked to-do. This is NOT a bug.

Comment:
If this new aspect of the bug reported by me is confirmed then the title of this bug should change.
Comment 6 Michael Leupold 2008-11-09 23:30:29 UTC
Both types of behaviour are still reproducible using trunk r881868.
Comment 7 Laurent Montel 2015-04-12 10:25:38 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.