234794 - sorting messages by "Status" should use logical (New > Unread > Read > Forwarded > Replied) instead of alphabetic order

Status: RESOLVED EXPIRED

(SeaMonkey :: MailNews: Message Display, enhancement)

Description

[Mad Max]

User-Agent:       
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030630

when sorting messages by Status (instead of Date or Subject or Sender so),
the "New" messages are at top, then come the "Read", and the "Unread" are
at the bottom.
Mozilla seems to use alphabetical ordering, I think that 
something like New > Unread > Read > Forwarded > Replied
would in general be closer to the expected result.

(maybe not everybody will agree on this... I admit that for searching the bunch
of Forwarded messages in between all others, it may not be obvious to look
in-between "Read" and "Replied".
As always, a nice solution to this dilemma would be to make this order
"customizable" in the "Preferences..." Menu.


Reproducible: Always
Steps to Reproduce:
1. send yourself 2 messages, read only one of them
2. send yourself a third message
3. click "Get Msgs", then click on "Status" to sort by status

Actual Results:  
 the "New" will be at the opposite end than the "Unread"


Expected Results:  
The "Unread" should be in between "New" and "Read"
(e.g. if the "new" ones are at the top, the "Unread" should follow)

Comment 1

[timeless]

personally I either sort by the "read" column [in classic theme it's a green
widget] which does read>unread>new, or by thread with view>threads>unread.

However, looking at my status column, I can't imagine wanting the order you're
suggesting. 

fwiw the current order /seems/ to be:
New, Replied, Forwarded, Read, Unread

Which is *not* alphabetical. Actually burrying the read messages in the middle
seems to work well for me, here's an approximate number list:

19new, 7replied, 2forwarded, 20read(in this session), 1105unread
not displayed: somewhere over 200,000 read messages.

If I wanted to show *all* of my messages, I'd like to be able to look at them in
two groups: important (new, replied, forwarded), and notable (unread) - yes
there's another group, but, I have no plan to read anything there unless I'm
asked to do research.

IOW, I'm on the WONTFIX side of the fence.

Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7a) Gecko/20040215

Reporter: you're using 1.4 which is too old to report bugs against, in the
future, please try using a current release (1.6 is the current release).

Comment 2

[Gervase Markham [:gerv]]

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/

Comment 3

[Gervase Markham [:gerv]]

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.