288580 - Request action for Mark Entire Thread Unread

Status: RESOLVED EXPIRED

(Thunderbird :: Mail Window Front End, enhancement)

Description

[bugzilla]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040207 Firefox/0.8
Build Identifier: Thunderbird 1.0.2 (20050317?)

It appears that it's not possible to mark an entire thread unread.  When
right-clicking on the collapsed thread item in the message list, there is no
"mark -> thread as unread" option visible; nor does choosing mark -> thread as
read toggle the read setting for the thread.  It is possible to mark the
individual message selected as read or unread with the mark -> read toggle.

Reproducible: Always

Steps to Reproduce:
1. Right-click a message in a thread.
2. Click the Mark sub-menu
Actual Results:  
There is no "Mark thread as unread" option in either the expanded or collapsed
thread view.

Expected Results:  
There should be a "Mark thread as unread" option in both the expanded and
collapsed view when right-clicking on a message in a threaded view.

Comment 1

[zug_treno]

For a possible workaround, see bug 210442 comment 1.

Comment 2

[bugzilla]

(In reply to comment #1)
> For a possible workaround, see bug 210442 comment 1.

True.  But mark-thread-unread should be a single operation of its own, not a
derivative of a series of other operations.  This has been changed to
"enhancement", but I'd argue it should still get higher priority than say,
prettifying a widget or redoing a dialog box layout.

It's technically a "new feature request", but given that "mark thread read" is
already implemented, and every newsreader written in the last umpteen years has
had threading and mark-thread-read/unread, I submit that its absence is as much
an actual bug as the lack of a "mark messages read" option would be.

Comment 3

[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 4

[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.