Wrong 'total' and 'unread' number in saved search folders in some cases

RESOLVED INCOMPLETE

Status

Thunderbird
Mail Window Front End
--
minor
RESOLVED INCOMPLETE
13 years ago
8 years ago

People

(Reporter: Matjaz, Unassigned)

Tracking

(Blocks: 1 bug)

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: closeme 2010-04-29)

(Reporter)

Description

13 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6

In some cases in saved search folders the number of unread and the total number
of messages are wrong. This happens sometimes when you do a search on a folder
that is deeper in hierarhy, but this is not always the case. If this bug appears
when creating a saved search based on some folder, I can always reproduce this
on that particular folder.

Reproducible: Sometimes

Steps to Reproduce:
1. Right-click on some folder
2. Choose search messages
3. Do a search and save as saved search folder (in suggested location)

Actual Results:  
When you open a saved search folder, "total' and 'unread' counter are wrong -
that are exactly the same as counters in folder that was searched.
(Reporter)

Comment 1

13 years ago
Ok, I think I've discovered under which conditions this occurs.

1. It occurs when you search a folder that has no subfolders.
2. It occurs when you search a folder that has subfolders but you choose not to
search subfolders.

Do this:
1. Folder structure
A
   B
       C

2. Right-click on folder B and select "search messages"
3. Do a search and save as search folder
4. Repeat, this time uncheck "search subfolders"
5. See the difference in counters
QA Contact: front-end

Updated

10 years ago
Blocks: 438257

Updated

10 years ago
Assignee: mscott → nobody

Comment 2

10 years ago
 Matjaz, do you see this when using version 2?
Severity: normal → minor
Summary: Wrong 'total' and 'unread' number in saved search fodlers in some cases → Wrong 'total' and 'unread' number in saved search folders in some cases

Comment 3

10 years ago
Here is an example of this problem in Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1b3pre) Gecko/20090121 Shredder/3.0b2pre: saved search is stil marked as containing new message after you move this message to another folder (junk mail for example).

Comment 4

9 years ago
Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1b3pre) Gecko/20090223 Thunderbird/3.0b2

Same issue here.

I have all mail in the inbox and use search folders based on rules and tags.
The total unread is wrong all the time, until I click the search folder and the the number is instantly corrected.  This bug was present in all versions of 2 as well.

I'm fairly certain that it caused because one of the rules marks certain emails as read, but the totals are not updated at this point.

Comment 5

9 years ago
i cannot reproduce this on windows vista business, build 

Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.2pre) Gecko/20090724 Shredder/3.0b4pre ID:20090724050314

please provide more detailed steps and screenshots
Matjaz and\or James what about comment #5?
Using latest TB 3.0.4 the bug is gone as in comment #5?
Whiteboard: closeme 2010-04-29

Comment 7

8 years ago
I haven't noticed it recently, although I have recently moved to 3.1b1 due to some issues with 3.0.x and dramatically cut down my use of search folders.

Is it worth me doing any testing for this bug in lanikai 3.1b1?
(In reply to comment #7)
> I haven't noticed it recently, although I have recently moved to 3.1b1 due to
> some issues with 3.0.x and dramatically cut down my use of search folders.
> 
> Is it worth me doing any testing for this bug in lanikai 3.1b1?

Yes
RESOLVED INCOMPLETE due to lack of response to last question. If you feel this change was made in error, please respond to this bug with your reasons why.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.