After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 569917 - Error with "move to folder" filter when folder is 2 levels deep in folders hierarchy
Error with "move to folder" filter when folder is 2 levels deep in folders hi...
Status: RESOLVED DUPLICATE of bug 214238
Product: evolution
Classification: Applications
Component: Mailer
2.24.x (obsolete)
Other All
: Normal normal
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2009-01-30 22:55 UTC by bohtvaroh
Modified: 2009-12-29 10:58 UTC
See Also:
GNOME target: ---
GNOME version: 2.23/2.24


Description bohtvaroh 2009-01-30 22:55:52 UTC 
Please describe the problem:
When using message filters with "Then" criteria set to "Move to folder" and this folder is 2 (or more) level deep in folders hierarchy (e.g. Inbox/Mailing lists/erlang-questions) than when new mail arrives folder is not shown in bold text with new messages quantity. To view this we need to click on this folder.

Steps to reproduce:
1. Create message filter which moves mail to a folder 2 level deep in folders hierarchy (e.g. Inbox/Mailing lists/erlang-questions)
2. Check for mail with this criteria
3. No bold text. We need to click on the folder (erlang-questions)


Actual results:
I see no new messages info in the interface

Expected results:
Folder should be shown with bold text with messages quantity.

Does this happen every time?
Yep.

Other information:
Comment 1 Akhil Laddha 2009-12-29 10:58:47 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.

*** This bug has been marked as a duplicate of bug 214238 ***