73562 - View -> Messages -> Watched Threads (ALL - not just the unread ones)

Status: NEW

(SeaMonkey :: MailNews: Message Display, enhancement)

Description

[Peter Lairo]

Mozilla/5.0 (Windows; U; WinNT4.0; en-US; 0.8.1) Gecko/20010321

Need: View -> Messages -> Watched Thread (WITHOUT Unread)

When i want to see my watched threads, i prefer to see ALL my watched threads
(not just the unread ones). This is very useful for reviewing threads that are
relevant to me and where i might need to "encourage" a response or where i need
to find alternate solutions because no-one is responding to a perticulat thread
in that newsgroup. It is also useful for reviewing *all* topics I have posted
on, to jar my memory on things i may have forgotten.

Please either change to: View -> *Messages -> Watched Thread (WITHOUT Unread)*
or add the *(WITHOUT Unread)* as an item to the menu. :)

*View -> Messages -> Watched Thread (WITHOUT Unread)*

Comment 1

[Peter Lairo]

OOPS, actually, the menu should just read:

*View -> Messages -> Watched Threads*

Comment 2

[Keyser Sose]

Marking NEW.

Comment 3

[rolfleggewie]

This appears to be a dupe of bug 80261.

Comment 4

[Peter Lairo]

*** Bug 80261 has been marked as a duplicate of this bug. ***

Comment 5

[Peter Lairo]

esther, hope you don't mind :)

Comment 6

[Peter Lairo]

The menu could look like this:

SUB-MENU (View - Messages):
+-----------------------------+
| All                         |
| Unread                      |
| Threads with unread         |
| Watched Threads             |<-----This one !!!
| Watched Threads with Unread |
+-----------------------------+

Comment 7

[Peter Lairo]

changing summary to (hopefully) be more clear:

OLD: [RFE] View -> Messages -> Watched Thread (WITHOUT Unread)
NEW: [RFE] View -> Messages -> Watched Threads (ALL - not just the unread ones)

Comment 8

[Kenneth]

Is anything being done on this seemingly simple modification?  This simple
change would help things tremendously when reviewing old newsgroup threads that
may not necessarily have new messages.

Comment 9

[Peter Lairo]

renominating for 1.3

Removing "helpwanted" because it didn't help for over a year now. :(

Comment 10

[Samir Gehani]

Mail triage team: nsbeta1-

Comment 11

[Matthew Elvey]

Yeah, it is so lame that this is missing.  
Is there a workaround (via a prefs file edit,...)?  
Maybe it's one of those bugs that doesn't need a real code change to fix.

Also, 
SUB-MENU (View - Messages):
+-----------------------------+
| All                         |
| Unread                      |
| Threads                     |<another suggestion*
| Threads with unread         |
| Watched Threads             |<-----This one !!!
| Watched Threads with Unread |
+-----------------------------+
 
*guess I should open a bug for this, unless there's one already, or unless
there's agreeement to add it to this bug.

Comment 12

[Kenneth]

Why can't we get this bug fixed for 1.4?  Seems like such a minor thing.  We 
already have even MORE functionality in that the existing menu option shows 
Watched with UNREAD... is it too much to ask to have one that just shows 
WATCHED???

Comment 13

[Matthew Elvey]

You're part of 'we'.  I think this doesn't need a real code change to fix, as I
said.  Give it a try.  No whining.  PS There's a lot of upheaval due to the new
roadmap.

Comment 14

[bugzilla]

Would be a really usefull enhancement.

Comment 15

[Robert Kaiser]

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 16

[Robert Kaiser]

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 17

[Robert Kaiser]

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 18

[Robert Kaiser]

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 19

[Robert Kaiser]

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 20

[Peter Lairo]

This bug still applies to Seamonkey (and to Thunderbird). Please re-confirm it (and change to "MailNews Core").

Comment 21

[Stewart Gordon]

Is there any component in MailNews Core that's actually appropriate to this?

Comment 22

[Wayne Mery (:wsmwk)]

(In reply to comment #21)
> Is there any component in MailNews Core that's actually appropriate to this?

It is sufficient to leave this in seamonkey. bug 294901 is already there for thunderbird/core. reversing the dependency

Comment 23

[Robert Kaiser]

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614