capabilities of forthcoming group changes

[Joel Peshkin]

Gervase Markham wrote:

> Rob Browning wrote:
>
>> I can create product "foo", "client-a-group", and "client-b-group",
>> and then I can arrange it so that everyone is in the foo product group
>> and the appropriate people are in the client-a and client-b groups.  I
>> can also arrange it so that all "foo" bugs end up in the "foo" group,
>> but I can't see a way to insist that all bugs submitted by people in
>> the client-a group also end up in the client-a group.  They can always
>> just unclick their client-a group when they create a bug.
>
>
> Can you not set both MemberControl and OtherControl to Mandatory in 
> the Group Controls section, found via editproducts.cgi?
>
> Gerv


Only if you have a distinct product for client-a and client-b.

Otherwise, anyone creating a bug in a shared product would be forced to 
restrict it to ONLY people who are members of both client-a and client-b.

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.

-Joel