151624 - Checkbox matrix needs duplication removed

Status: RESOLVED WONTFIX

(Bugzilla :: User Interface, defect)

Description

[Felix Miata]

2002061209 OS/2 trunk

I went to prefs to confirm no checks in "CC field changes" boxes shortly after
Mozilla upgraded Bugzilla to 2.17. I committed changes even though finding no
changes necessary. Immediately after, I removed myself from CC on 8 bugs. I got
bugmail notification of my email removed from CC on all those 8 bugs.

Comment 1

[Bradley Baetz (:bbaetz)]

IS the checkbox for:

"I'm added to or removed from this capacity" checked in the CC column?

Comment 2

[Felix Miata]

Yes, so I guess this bug isn't defined properly. When I looked at the row for CC
changes, it became apparent that I had found what I thought I was looking for
and stopped looking. What we have is multiple paths to the same result. I don't
see a best way to get rid of it, but two paths to the same place shouldn't be. I
guess at least one of the cells in the matrix should be blank, probably row 7,
column 4.

Comment 3

[Bradley Baetz (:bbaetz)]

Yeah, it could be descibed a bit better.

The reason for doing it this way is that if someone ccs me on a bug for comment,
I want to know, but if they cc someone else, I don't care.

Comment 4

[Dave Miller [:justdave]]

The User Interface component now belongs to Gerv.  Reassigning all UNCONFIRMED
and NEW (but not ASSIGNED) bugs currently owned by Myk (the previous component
owner) to Gerv.

Comment 5

[Dave Miller [:justdave]]

Reassigning back to Myk.  That stuff about Gerv taking over the User Interface
component turned out to be short-lived.  Please pardon our confusion, and I'm
very sorry about the spam.

Comment 6

[Myk Melez [:myk] [@mykmelez]]

Not sure there's a fix for the duplicate path problem (cc:ing gerv, who may be
redesigning the form ala bug 128839, for his thoughts), but we could add a note
that "added or removed from cc field" overrides "cc field changes".

Comment 7

[Gervase Markham [:gerv]]

I think the trick here is to establish a priority ordering. I am already doing
that in the new world over in bug 73665, for the relationships to the bug. I
guess we also need one (or to make explicit the existing implicit one) for the
changes that can happen.

Is this the only case where there's this overlap?

We can't blank out row 7, column 4 - it has a use. What if the CC field changes,
but the change does not involve you? You need a checkbox in that position. And I
can see people saying "I'm not interested in CC changes in general, but I am
interested if someone adds me to or removes me from the CC of a bug."

Gerv

Comment 8

[Dave Miller [:justdave]]

Pushing out bugs that aren't blockers.  If someone's working on one of these, we
can move it back.

Comment 9

[Max Kanat-Alexander]

This bug has not been touched by its owner in over six months, even though it is
targeted to 2.20, for which the freeze is 10 days away. Unsetting the target
milestone, on the assumption that nobody is actually working on it or has any
plans to soon.

If you are the owner, and you plan to work on the bug, please give it a real
target milestone. If you are the owner, and you do *not* plan to work on it,
please reassign it to [e-mail] or a .bugs component owner. If you are
*anybody*, and you get this comment, and *you* plan to work on the bug, please
reassign it to yourself if you have the ability.

Comment 10

[Gervase Markham [:gerv]]

Email prefs are additive; you get email if there's _any_ reason you should get
it. So having either of "added/removed from CC" and "CC field changes" checked
will get you mail.

There are no plans to change how this works any further; so is this a WONTFIX? I
can't see it being worth adding explanatory text either.

Gerv

Comment 11

[Frédéric Buclin]

(In reply to comment #10)
> There are no plans to change how this works any further; so is this a WONTFIX?

Yes, the OR relationship between conditions makes that you get bugmail as soon as at least one condition is met, which is the case here. So the behavior is correct -> WONTFIX.