Closed Bug 551136 Opened 15 years ago Closed 14 years ago

"Recent folders" pane doesn't present the folders sorted Alphabetically

Categories

(Thunderbird :: Folder and Message Lists, defect)

x86
macOS
defect
Not set
major

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 534523

People

(Reporter: william.allen.simpson, Unassigned)

Details

(Keywords: regression)

User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.2) Gecko/20100115 Firefox/3.6 Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1.8) Gecko/20100227 Thunderbird/3.0.3 The recent folders window/pane is not sorted in 3.0. This makes the feature much harder to use. It was properly sorted in 2.0. Reproducible: Always Steps to Reproduce: 1. Starting with "All Folders", click the left arrow until "Recent Folders" appears. 2. 3. Actual Results: Not sorted alphabetically. Expected Results: Sort alphabetically, regardless of account. I have ~100 message filters to put new messages into appropriate folders. There are ~2000 folders after years of archiving. It is very hard to find new incoming messages without the properly updated Recent Folders that was present in previous versions. For those of us that get ~500 messages per day on 7 accounts, this is really annoying!
Component: General → Folder and Message Lists
QA Contact: general → folders-message-lists
Version: unspecified → 3.0
Related to bug 534523?
Gary can you hunt the regression window ?
Summary: [regression] recent folders pane not sorted → "Recent folders" pane doesn't present the folders sorted Alphabetically
william.allen.simpson, please see bug 534523 comment 3. Is this something you can do?
This also occurs under Windows 7. It was sorted properly under the prior version of Thunderbird for Windows.
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → DUPLICATE
left side of screen shot attachment 498771 [details] from bug 534523 confirms this is fixed. And it is also WFM in v5/v6
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.