"Set Status" filter just doesn't work

Bug #38477 reported by GonzO
8
Affects Status Importance Assigned to Milestone
Evolution
Invalid
Low
evolution (Ubuntu)
Invalid
Low
Ubuntu Desktop Bugs

Bug Description

I have a rule in Evolution that goes like this:

When any message with "SRC:" in the subject line comes in, do the following:

- Move it to FolderX
- Set its status to "read"

The first part works just fine - but the second part, setting the status to "read", has never worked. All of the messages are still in bold, still showing as unread.

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thanks for your bug. That works fine for me. What version of Ubuntu do you use? Do you use the filter on a local or imap account?

Changed in evolution:
assignee: nobody → desktop-bugs
status: Unconfirmed → Needs Info
Revision history for this message
GonzO (gonzo) wrote :

Dapper, all packages updated about five minutes ago (Tuesday, April 18, 3:36PM Central Standard Time [USA]).

This pair of filters are set for the Evolution Exchange server at my place of employment. (PS: Exchange works FAR better under Dapper than it ever did in Breezy. I daresay its awesome.)

Revision history for this message
Sebastien Bacher (seb128) wrote :

is that issue exchange specific maybe?

Revision history for this message
GonzO (gonzo) wrote :

No, doesn't seem to be. Created a new filter with the same rules applying to a POP account - same result. I have screenshots, as soon as I figure out how to add them I can show you...

Revision history for this message
Sebastien Bacher (seb128) wrote :

I've forwarded the issue upstream: http://bugzilla.gnome.org/show_bug.cgi?id=341777

Changed in evolution:
status: Needs Info → Confirmed
Revision history for this message
Sebastien Bacher (seb128) wrote :

comment from upstream:

"would be interesting to know if it worked in the other order:
- Set its status to "read"
- Move it to FolderX"

Works fine for me with the other order

Revision history for this message
Sebastien Bacher (seb128) wrote :

upstream has rejected the bug, doing the same. You can read the upstream bug for explanations on the topic

Changed in evolution:
status: Confirmed → Rejected
Revision history for this message
rhi (rhi-deactivatedaccount) wrote :

Please re-open and take a stand at upstream. For reasons, see the upstream bug.

It quite can't be expected from a non-hacker to understand why mark & then move works while moving & then marking doesn't. Even if this behaviour which does not accord to the Gnome User Interface Guidlines cannot be avoided, a warning message and the hint that the user should reverse the command order would be necessary.

I met several non-hacking people using Evolution and they all had this problem and considered this as a bug.

Revision history for this message
pc345 (randomjoe) wrote :

Agreed. This should never have been marked as invalid.

Its ok saying there is a workaround, but that doesnt exclude the fact that the underlying problem is infact a bug.

The bug was reported in 2006, and its still causing usability issues 2 years later

Changed in evolution:
importance: Unknown → Low
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.