4
>Groups and Group Security</TITLE
7
CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
9
TITLE="The Bugzilla Guide - 2.16.4 Release"
10
HREF="index.html"><LINK
12
TITLE="Administering Bugzilla"
13
HREF="administration.html"><LINK
16
HREF="voting.html"><LINK
18
TITLE="Bugzilla Security"
19
HREF="security.html"></HEAD
30
SUMMARY="Header navigation table"
39
>The Bugzilla Guide - 2.16.4 Release</TH
55
>Chapter 5. Administering Bugzilla</TD
77
>5.5. Groups and Group Security</H1
79
>Groups allow the administrator
80
to isolate bugs or products that should only be seen by certain people.
81
There are two types of group - Generic Groups, and Product-Based Groups.
84
> Product-Based Groups are matched with products, and allow you to restrict
85
access to bugs on a per-product basis. They are enabled using the
86
usebuggroups Param. Turning on the usebuggroupsentry
87
Param will mean bugs automatically get added to their product group when
91
> Generic Groups have no special relationship to products;
92
you create them, and put bugs in them
93
as required. One example of the use of Generic Groups
94
is Mozilla's "Security" group,
95
into which security-sensitive bugs are placed until fixed. Only the
96
Mozilla Security Team are members of this group.
99
>To create Generic Groups:</P
107
link in the footer.</P
111
>Take a moment to understand the instructions on the "Edit
112
Groups" screen, then select the "Add Group" link.</P
116
>Fill out the "New Name", "New Description", and
117
"New User RegExp" fields. "New User RegExp" allows you to automatically
118
place all users who fulfill the Regular Expression into the new group.
119
When you have finished, click "Add".</P
123
>To use Product-Based Groups:</P
130
>Turn on "usebuggroups" and "usebuggroupsentry" in the "Edit
131
Parameters" screen.</P
146
SRC="../images/warning.gif"
153
>XXX is this still true?
154
"usebuggroupsentry" has the capacity to prevent the
155
administrative user from directly altering bugs because of
156
conflicting group permissions. If you plan on using
157
"usebuggroupsentry", you should plan on restricting
158
administrative account usage to administrative duties only. In
159
other words, manage bugs with an unpriveleged user account, and
160
manage users, groups, Products, etc. with the administrative
169
>In future, when you create a Product, a matching group will be
170
automatically created. If you need to add a Product Group to
171
a Product which was created before you turned on usebuggroups,
172
then simply create a new group, as outlined above, with the
173
same name as the Product.</P
190
SRC="../images/warning.gif"
197
>Bugzilla currently has a limit of 64 groups per installation. If
198
you have more than about 50 products, you should consider
199
running multiple Bugzillas. Ask in the newsgroup for other
200
suggestions for working around this restriction.</P
206
> Note that group permissions are such that you need to be a member
209
> the groups a bug is in, for whatever
210
reason, to see that bug.
218
SUMMARY="Footer navigation table"
263
HREF="administration.html"
271
>Bugzilla Security</TD
b'\\ No newline at end of file'
added
removed
docs/html/groups.html
