Open Bug 214286 Opened 21 years ago Updated 15 years ago

[META] Improve functionality, usefulness and reliability of thread watching

Categories

(SeaMonkey :: MailNews: Message Display, defect)

Product:
SeaMonkey
Component:
MailNews: Message Display
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

People

(Reporter: smjg, Unassigned)

References

(Depends on 8 open bugs, Blocks 1 open bug)

Details

(Keywords: meta) 

This is a tracker for bugs and RFEs affecting the performance and usefulness of
the Watch Thread function.

Bug 11048 - Auto-watch threads you've posted to
Bug 73562 - [RFE] View -> Messages -> Watched Threads (ALL - not just the unread
ones)
Bug 112833 - RFE: Not possible to watch/ignore multiple threads
Bug 121664 - Unignored threads never properly returned to All or Unread Threads view
Bug 123121 - LABELING after WATCHING message removes WATCH?
Bug 127692 - Folder Pane should highlight Newsgroups with new (unread) messages
in watched threads
Bug 164081 - Display watched threads more prominently
Bug 184231 - "view" dropdown should include "Watched"
Bug 191298 - [META] Tracker for watch/ignore icon problems
Oops ... darn bug 40896 again!  Bug 121664 was supposed to be bug 121164.
Depends on: 121164
No longer depends on: 121664
Depends on: 184231
Bug 218208 - [mailviews] Watch/ignore status of thread should be available as
view condition
Depends on: 218208
Blocks: 236849
Product: Browser → Seamonkey
Depends on: 91052
Assignee: smjg → nobody
QA Contact: esther → message-display
MASS-CHANGE:
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
Status: NEW → UNCONFIRMED
Trying to expire a meta bug doesn't make any sense - we need to look at the
dependent bugs individually.
Status: UNCONFIRMED → NEW
You need to log in before you can comment on or make changes to this bug.