From f0324c374c51b61a8615044631337a60eb9a37a8 Mon Sep 17 00:00:00 2001
From: "jake%bugzilla.org" <>
Date: Fri, 3 Jan 2003 01:29:23 +0000
Subject: Recomiple the docs for the 2.17.3 release

---
 docs/html/groups.html | 146 ++++++++++++++++++++++++++++++++++++--------------
 1 file changed, 106 insertions(+), 40 deletions(-)

(limited to 'docs/html/groups.html')

diff --git a/docs/html/groups.html b/docs/html/groups.html
index 94f324fdc..8d6d01f66 100644
--- a/docs/html/groups.html
+++ b/docs/html/groups.html
@@ -79,45 +79,120 @@ NAME="groups"
 ><P
 >Groups allow the administrator
     to isolate bugs or products that should only be seen by certain people.
-    There are two types of group - Generic Groups, and Product-Based Groups.
+    The association between products and groups is controlled from
+    the product edit page under <SPAN
+CLASS="QUOTE"
+>"Edit Group Controls."</SPAN
+>
     </P
 ><P
->&#13;    Product-Based Groups are matched with products, and allow you to restrict
-    access to bugs on a per-product basis. They are enabled using the 
-    usebuggroups Param. Turning on the usebuggroupsentry
-    Param will mean bugs automatically get added to their product group when 
-    filed.   
+>&#13;    If the makeproductgroups param is on, a new group will be automatically
+    created for every new product.
     </P
 ><P
->&#13;    Generic Groups have no special relationship to products; 
-    you create them, and put bugs in them
-    as required. One example of the use of Generic Groups 
-    is Mozilla's "Security" group,
-    into which security-sensitive bugs are placed until fixed. Only the
-    Mozilla Security Team are members of this group.
+>&#13;    On the product edit page, there is a page to edit the 
+    <SPAN
+CLASS="QUOTE"
+>"Group Controls"</SPAN
+> 
+    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. 
     </P
 ><P
->To create Generic Groups:</P
+>&#13;    For each group, it is possible to specify if membership in that
+    group is...
+    </P
 ><P
 ></P
 ><OL
 TYPE="1"
 ><LI
 ><P
->Select the "groups"
+>&#13;        required for bug entry, 
+        </P
+></LI
+><LI
+><P
+>&#13;        Not applicable to this product(NA),
+        a possible restriction for a member of the 
+        group to place on a bug in this product(Shown),
+        a default restriction for a member of the 
+        group to place on a bug in this product(Default),
+        or a mandatory restriction to be placed on bugs 
+        in this product(Mandatory).
+        </P
+></LI
+><LI
+><P
+>&#13;        Not applicable by non-members to this product(NA),
+        a possible restriction for a non-member of the 
+        group to place on a bug in this product(Shown),
+        a default restriction for a non-member of the 
+        group to place on a bug in this product(Default),
+        or a mandatory restriction to be placed on bugs 
+        in this product when entered by a non-member(Mandatory).
+        </P
+></LI
+><LI
+><P
+>&#13;        required in order to make <EM
+>any</EM
+> change
+        to bugs in this product <EM
+>including comments.</EM
+>
+        </P
+></LI
+></OL
+><P
+>To create Groups:</P
+><P
+></P
+><OL
+TYPE="1"
+><LI
+><P
+>Select the <SPAN
+CLASS="QUOTE"
+>"groups"</SPAN
+>
         link in the footer.</P
 ></LI
 ><LI
 ><P
->Take a moment to understand the instructions on the "Edit
-        Groups" screen, then select the "Add Group" link.</P
+>Take a moment to understand the instructions on the <SPAN
+CLASS="QUOTE"
+>"Edit
+        Groups"</SPAN
+> screen, then select the <SPAN
+CLASS="QUOTE"
+>"Add Group"</SPAN
+> link.</P
 ></LI
 ><LI
 ><P
->Fill out the "Group", "Description", and 
-        "User RegExp" fields. "New User RegExp" allows you to automatically
+>Fill out the <SPAN
+CLASS="QUOTE"
+>"Group"</SPAN
+>, <SPAN
+CLASS="QUOTE"
+>"Description"</SPAN
+>, 
+         and <SPAN
+CLASS="QUOTE"
+>"User RegExp"</SPAN
+> fields. 
+         <SPAN
+CLASS="QUOTE"
+>"User RegExp"</SPAN
+> allows you to automatically
          place all users who fulfill the Regular Expression into the new group. 
-         When you have finished, click "Add".</P
+         When you have finished, click <SPAN
+CLASS="QUOTE"
+>"Add"</SPAN
+>.</P
 ><DIV
 CLASS="warning"
 ><P
@@ -157,31 +232,22 @@ VALIGN="TOP"
 ></LI
 ></OL
 ><P
->To use Product-Based Groups:</P
-><P
-></P
-><OL
-TYPE="1"
-><LI
-><P
->Turn on "usebuggroups" and "usebuggroupsentry" in the "Edit
-        Parameters" screen.</P
-></LI
-><LI
-><P
->In future, when you create a Product, a matching group will be
-        automatically created. If you need to add a Product Group to
-        a Product which was created before you turned on usebuggroups,
-        then simply create a new group, as outlined above, with the
-        same name as the Product.</P
-></LI
-></OL
-><P
 >&#13;      Note that group permissions are such that you need to be a member
       of <EM
 >all</EM
 > the groups a bug is in, for whatever
-      reason, to see that bug.
+      reason, to see that bug. Similarly, you must be a member 
+      of <EM
+>all</EM
+> of the entry groups for a product 
+      to add bugs to a product and you must be a member 
+      of <EM
+>all</EM
+> of the canedit groups for a product
+      in order to make <EM
+>any</EM
+> change to bugs in that
+      product.
     </P
 ></DIV
 ><DIV
-- 
cgit v1.2.3-24-g4f1b