capabilities of forthcoming group changes

[Joel Peshkin]

>
>
>
>So with 2.17.4, is there an intended way to handle multiple clients
>(multiple client groups) submitting bugs for a given product?
>
>Ideally members of one client group shoudn't be able to see bugs
>submitted by other clients (unless the admin takes some kind of
>action), and members of a given client group couldn't accidentally or
>intentionally submit a public bug.
>  
>
The only way to do this today is to use one product per client.  The 
options are explained in the editproducts page for editing group controls.

Forcing restrictions based on the membership of the submitter saying 
that Group A must restrict to Group A but they don't have to if they are 
members of both Group A and Group B would be an interesting trick. 
 After all, your own staff will need to be members of all of these 
groups and their membership should not require them to restrict bugs to 
be visible by only other people who are members of all of the groups.

If anyone has an idea of a consistent way to express this, jump in anytime.

-Joel