299895 - Make insider groups generic as a list of groups configurable per product

Status: NEW

(Bugzilla :: Administration, task, P2)

Description

[timeless]

> can someone please explain why we have _one_ insider group?
> why can't each product allow a list of groups to mark creatures as insiders
+for its bugs

Comment 1

[timeless]

mozilla "helped" me submit this bug (way too early).

each product should be allowed to list groups that are allowed to mark comments
as for people in its group.

this would allow drivers to discuss a bug privately at the same time as the
security group privately discusses it.

Comment 2

[timeless]

dveditz expressed an interest in having this feature enabled for bmo, but of course this bug is blocking that. can we try to scare up a hacker to fix this?

Comment 3

[Daniel Veditz [:dveditz]]

Well, not exactly blocking... :-) If security group were the insidergroup on BMO I'd be happy, but I bet the other groups wanting that status wouldn't be. But maybe they wouldn't know what they were missing.

Comment 4

[Frédéric Buclin]

OK, I want this asap. I realized that some guys of the Core security group are marking some comments in bugs being in the Bugzilla product as private which prevents me from reading them (as I'm not in this specific security group), which irritates me A LOT. With this RFE implemented, each security group will be able to manage their own bugs and comments being in their respective products.

Comment 5

[Frédéric Buclin]

Just one thing: how are private comments supposed to behave when moving a bug from one product which has an insidergroup to another product which hasn't? Clearing the "private" bit would make the comments public. One could use it (even accidentally, as he may not know that some comments are private) to make comments he cannot read public.

Comment 6

[Max Kanat-Alexander]

(In reply to comment #5)
> Clearing the "private" bit would make the comments public. One could use it
> (even accidentally, as he may not know that some comments are private) to make
> comments he cannot read public.

  I think in this case we'll have to display a warning on the Verify New Product page.

Comment 7

[Frédéric Buclin]

Note to self: fulltext search introduces some big problems with this feature, due to the way it's implemented.