bugzilla.mozilla.org will be intermittently unavailable on Saturday, March 24th, from 16:00 until 20:00 UTC.

Confirm comment on groupset change.




Creating/Changing Bugs
17 years ago
10 years ago


(Reporter: CodeMachine, Unassigned)





17 years ago
When you make a comment and change the groupset, the changes should go out to
the people who could previously read the bug.

Hence, if you add a comment and change group, we should warn the changer of this
and confirm their action to be sure their comment does not divulge confidential

I believe currently this is broken - changemails don't go out to the people who
could previously see the bug.


17 years ago
Depends on: 97469


17 years ago
Summary: CConfirm comment on groupset change. → Confirm comment on groupset change.


17 years ago
Priority: -- → P3
Target Milestone: --- → Bugzilla 2.16
We are currently trying to wrap up Bugzilla 2.16.  We are now close enough to
release time that anything that wasn't already ranked at P1 isn't going to make
the cut.  Thus this is being retargetted at 2.18.  If you strongly disagree with
this retargetting, please comment, however, be aware that we only have about 2
weeks left to review and test anything at this point, and we intend to devote
this time to the remaining bugs that were designated as release blockers.
Target Milestone: Bugzilla 2.16 → Bugzilla 2.18

Comment 2

14 years ago
These unloved bugs have been sitting untouched since June 2002 or longer.  If
nobody does anything else to them, they certainly won't make 2.18
Retargetting to 2.20.  If you really plan to push them right now, you might pull
them back in.
Target Milestone: Bugzilla 2.18 → Bugzilla 2.20

Comment 3

13 years ago
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 nobody@bugzilla.org 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.
Target Milestone: Bugzilla 2.20 → ---


12 years ago
QA Contact: mattyt-bugzilla → default-qa


11 years ago
Assignee: myk → create-and-change

Comment 4

10 years ago
If the bug is restricted to a group, then the purpose is to not let other users see it anymore. So we don't want to email them.
Last Resolved: 10 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.