CVS tip - major checkin - Rearchitected Product Groups

Joel Peshkin bugreport at peshkin.net
Sun Nov 24 20:12:47 UTC 2002


All:

   Bug 147275 has finally landed.  In the CVS tip, the entire mechanism 
for handling groups has been revised.

   First, it is intended to be backwards-compatible so that you should 
be able to completely ignore the new capabilties and Bugzilla will 
default to setting group controls just the way that were always done 
before.

    However, it is now possible to exert much more control over how 
groups and products are related.  In editproducts.cgi, there is now a 
mechnaism to permit you to edit the "Group Controls" for a product and 
determine which groups are applicable, default, and mandatory for each 
product as well as controlling entry for each product and being able to 
set bugs in a product to be totally read-only unless some group 
restrictions are met.

    Example: When several products need to be associated with the same 
default group (formerly a product group), instead of defining several 
groups with the same names as the products and managing memberships in 
each group, a single group can be defined to control access and that 
group can be set as a "Default" group for all of the products.

   Example:  If certain products are never supposed to have a publically 
accessible bug, define a group of all authorized users and set the 
groups control for those products to indicate that the group is 
Mandatory/Mandatory.  This will place bugs in that group without giving 
the user any option at all.

  Example: Anyonce can enter a security bug.  Create a product for 
security bugs. Do not restrict entry to the product at all. However, set 
the Member/Nonmember permissions to Default/Mandatory.  This will permit 
anyone to enter and members of the security group will be able to 
override the default group restriction while nonmembers will be forced 
to restrict the bug to the security group.

    The list of possible scenarios goes on.  I am rather certain that 
some scenarios have not been anticipated.  If you file any bugs on this 
for either further enhancment or for regressions, please copy me on the bug.

Thanks,

Joel Peshkin





More information about the developers mailing list