Bug 487262 - Vfolders with "status is not read" rules aren't usable anymore
Vfolders with "status is not read" rules aren't usable anymore
Status: CLOSED UPSTREAM
Product: Fedora
Classification: Fedora
Component: evolution (Show other bugs)
10
All Linux
low Severity medium
: ---
: ---
Assigned To: Matthew Barnes
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2009-02-25 00:43 EST by James Antill
Modified: 2010-03-10 15:40 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2009-02-25 08:54:39 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
GNOME Bugzilla 562912 None None None Never

  None (edit)
Description James Antill 2009-02-25 00:43:39 EST
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 00:44:28 EST
Ok, sorry for the stupid auto pkg = yum setting.
Comment 2 Milan Crha 2009-02-25 08:54:39 EST
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 15:40:07 EST
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.