capabilities of forthcoming group changes

[Rob Browning]

Joel Peshkin <bugreport at peshkin.net> writes:

> It is actually possible to set the group controls so that, for
> product "foo", a group for which neither group of clients is a
> member is Default/Mandatory.  This will mean that only the reporter
> and your own staff will be able to see a bug unless someone on your
> staff goes in and changes the permissions to allow the rest of the
> client group to see it.

OK, so I played around with this a bit more, and if I understood you
correctly, it won't work, at least not the way I thought you meant.

If you create a product foo, and a group "incoming" that's
Default/Mandatory for foo, but that none of the clients are a member
of, then none of the clients seem to be able to submit a bug to foo.
It's not offered as a product when creating a new bug -- I presume
this is because enter_bug.cgi is checking to see that the user has
permission for all the mandatory groups for a given product (in this
case including the incoming group).

-- 
Rob Browning
rlb @defaultvalue.org and @debian.org; previously @cs.utexas.edu
GPG starting 2002-11-03 = 14DD 432F AE39 534D B592  F9A0 25C8 D377 8C7E 73A4