Closed Bug 250537 Opened 20 years ago Closed 19 years ago

new feature: total count of unread messages of a folder with subfolders, accumulating the subfolders unread count

Categories

(Thunderbird :: Mail Window Front End, enhancement)

Other
All
enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: l.capriotti, Assigned: mscott)

Details

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040626 Firefox/0.9
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040626 Firefox/0.9

In the "local folders" I've created a main folder "a" and two subfolders "b" and
"c". Assuming folder "a" does not contain unread messages, folder "b" contains 2
unread messages - and is seen as "b (2)" in bold in the tree - while folder "c"
has 3 unread messages - thus is seen as "c (3)" in bold.
Now, folder "a" unread count ignores the 5 unread messages in the subfolders,
while I'd like to have the "a" folder showing as "a (5)" in bold.


Reproducible: Always
Steps to Reproduce:
1.create a folder "folder1" in local folders
2.create two subfolders "folder2" and "folder3" in "folder1"
3.populate the "folder2" with two unread messages
4.populate the "folder3" 1 two unread messages


Actual Results:  
unread count for "folder1" is 0 

Expected Results:  
unread count for "folder1" should be 3
Identical to bug 135092 for MailNews product.
Related to/duplicate of bug 235956?
Indeed it is a dupe.

*** This bug has been marked as a duplicate of 235956 ***
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → DUPLICATE
Sorry, I am mistaken, every so slightly.  This bug is about putting the 
children's unread count next to a *folder*; bug 235956 is about putting the 
unread count next to the *account* only.  A distinction without a difference in 
my mind, but I don't want to argue about it.

  250537 : 235956  ::  135092 : 199482
Status: RESOLVED → UNCONFIRMED
Resolution: DUPLICATE → ---
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago19 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.