From 11945a73c631bedbcf8daaba531964c3fc2d6333 Mon Sep 17 00:00:00 2001 From: "justdave%syndicomm.com" <> Date: Thu, 5 Feb 2004 12:49:08 +0000 Subject: - Remove html, txt, and pdf directories from CVS - makedocs.pl now creates said directories when building the docs The idea here is that it's useless to have compiled stuff in CVS. The website will now auto-build the docs upon changes to the xml directory. --- docs/html/groups.html | 320 -------------------------------------------------- 1 file changed, 320 deletions(-) delete mode 100644 docs/html/groups.html (limited to 'docs/html/groups.html') diff --git a/docs/html/groups.html b/docs/html/groups.html deleted file mode 100644 index 445ada184..000000000 --- a/docs/html/groups.html +++ /dev/null @@ -1,320 +0,0 @@ -Groups and Group Security
The Bugzilla Guide - 2.17.7 - Development Release
PrevChapter 3. Administering BugzillaNext

3.8. Groups and Group Security

Groups allow the administrator - to isolate bugs or products that should only be seen by certain people. - The association between products and groups is controlled from - the product edit page under "Edit Group Controls." -

If the makeproductgroups param is on, a new group will be automatically - created for every new product. -

On the product edit page, there is a page 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. -

For each group, it is possible to specify if membership in that - group is... -

  1. required for bug entry, -

  2. 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). -

  3. 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). -

  4. required in order to make any change - to bugs in this product including comments. -

To create Groups:

  1. Select the "groups" - link in the footer.

  2. Take a moment to understand the instructions on the "Edit - Groups" screen, then select the "Add Group" link.

  3. Fill out the "Group", "Description", - and "User RegExp" fields. - "User RegExp" allows you to automatically - place all users who fulfill the Regular Expression into the new group. - When you have finished, click "Add".

    If specifying a domain in the regexp, make sure you end - the regexp with a $. Otherwise, when granting access to - "@mycompany\.com", you will allow access to - 'badperson@mycompany.com.cracker.net'. You need to use - '@mycompany\.com$' as the regexp.

  4. After you add your new group, edit the new group. On the - edit page, you can specify other groups that should be included - in this group and which groups should be permitted to add and delete - users from this group.

Note that group permissions are such that you need to be a member - of all the groups a bug is in, for whatever - reason, to see that bug. Similarly, you must be a member - of all of the entry groups for a product - to add bugs to a product and you must be a member - of all of the canedit groups for a product - in order to make any change to bugs in that - product. -


PrevHomeNext
VotingUpUpgrading to New Releases
\ No newline at end of file -- cgit v1.2.1