Closed Bug 309401 Opened 19 years ago Closed 19 years ago

"Watch this bug" link when viewing a bug report

Categories

(Bugzilla :: User Interface, defect)

PowerPC
macOS
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: stian, Assigned: myk)

Details

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8b4) Gecko/20050908 Firefox/1.4
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8b4) Gecko/20050908 Firefox/1.4

When viewing a specific bug, for instance a bug about Mozilla proxy settings on
OS X, a user might decide he wants to follow this bug to be notified when any
progress (or lack of..) happens.

There is no appearant link "Watch this bug" or similar available when viewing a
bug. However, there is the CC list, where the user has to add his own email
address to the "Add to CC" field. 

The problem of this, in addition to being non-intuitive and requiring the user
to type in his own email address again, is that this sends out an email to all
the other Cc people about the addition of a Cc recipient, which should normally
be totally uninteresting and just spam.

In addition, the other watchers will think you are an idiot because you are
changing the bug without anything important being done.

Reproducible: Always

Steps to Reproduce:
1. View a bug
2. Add your self to the Cc list, press Enter

Actual Results:  
All the other people watching the bug got notified that I was also watching the bug.

Expected Results:  
There should be a seperate "Watch this bug" link/menu choice that adds the
logged in user's email address to the Cc list. This change is not important, and
the other CC people should therefore not get any notifications of this addition.
In 2.22 (it might also be in 2.20) there's an "Add Me to CC" check-box.

If you don't want to receive notifications when people just add themselves to
the CC list, there's an email preference for that.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.