201916 - ability to select bugs that your CCed on that you don't want to receive additional comments on

Status: VERIFIED DUPLICATE of bug 55108

(Bugzilla :: Email Notifications, defect)

Description

[NorthMan]

User-Agent:       Mozilla/5.0 (Windows 1991 Government Server Edition; en-US) Gecko
Build Identifier: 

After a while with being involved with Mozilla and Bugzilla, I've CCed myself to
many bugs.

Sometimes, some bugs just general a whole lot of traffic.  Take for example bug
32218.  I CCed myself.  I CC myself to bugs I want to keep track of.

However, sometimes a bug will just get a whole lot of comments, and you don't
want to deal with all those comments, because you don't care.

In this case, I still want to know, if say bug 32218 has been fixed, marked
invalid, has a patch attached, or if the OS or target milestone changes.  But I
no longer want to receive all those unending streams of additional comments
about the bug.

SUGGESTED FIX:

In the bugzilla user options have another tab/screen.

When you open this tab/screen, it will show all bugs that you are CCed to. 
There will be a checkbox beside each box, and all the checkboxes will be
checked.  You then can uncheck the boxes besides bugs which you do not want to
receive additional comments on.  You can also recheck boxes for bugs you want to
receive comments on again.

I'm sure there's a better or more elegant way, but this is how I imagined it.

Reproducible: Always

Steps to Reproduce:

Comment 1

[Ryan Pertusio]

a very useful feature, perhaps.

The only real issue I see is the potential drawback of extremely large lists.

Comment 2

[Dave Miller [:justdave]]

I suppose it wouldn't be too hard to handle with an additional column on the cc
table...

Probably dependent on a lot of the other email rewrite junk though (and probably
a dupe, I have a hard time believing no one's suggested this before)

Comment 3

[NorthMan]

I looked through every single bug's summary in the Bugzilla:Email Notifications
component, and saw no previous bug.   I could have missed it, but I thoroughly
checked for dups.

Comment 4

[J. Paul Reed [:preed]]

This is, indeed, a dup.

I found about 3 bugs tonight that are basically the same thing, although
expressed sort of differently.


*** This bug has been marked as a duplicate of 125538 ***

Comment 5

[Jesse Ruderman]

This is actually a dup of bug 55108.

Comment 6

[Jesse Ruderman]

*** This bug has been marked as a duplicate of 55108 ***

Comment 7

[NorthMan]

Alright, marking verified, but the bug this is being marked as a duplicate of is
asking for a much more narrow feature than this bug asks for.

So it's technically not a duplicate, but whatever.