Bug 487262 - Vfolders with "status is not read" rules aren't usable anymore
Summary: Vfolders with "status is not read" rules aren't usable anymore
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution
Version: 10
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-02-25 05:43 UTC by James Antill
Modified: 2010-03-10 20:40 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2009-02-25 13:54:39 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
GNOME Bugzilla 562912 0 None None None Never

Description James Antill 2009-02-25 05:43:39 UTC
Description of problem:
 If you have a Vfolder with a rule that says "status is not read", this used to mean that each time you moved into/out of the folder it would remove the messages you had read ... now it does it in "real time", which means the message you are reading is no longer in the folder, which means that evolution moves onto another message, which means that it too is now "read", ...
 This makes the "status is not read" rule worthless.

Version-Release number of selected component (if applicable):
evolution-0:2.24.4-1.fc10.x86_64

Comment 1 James Antill 2009-02-25 05:44:28 UTC
Ok, sorry for the stupid auto pkg = yum setting.

Comment 2 Milan Crha 2009-02-25 13:54:39 UTC
Thanks for the bug report, this is an outstanding issue with 2.24, which is reported upstream [1]. Closing as such.

[1] http://bugzilla.gnome.org/show_bug.cgi?id=562912

Comment 3 James Antill 2010-03-10 20:40:07 UTC
It's worth noting that "closed => upstream" means "we've moved this bug to the upstream GNOME BZ, and it is now rotting there".


Note You need to log in before you can comment on or make changes to this bug.