diff options
author | justdave%syndicomm.com <> | 2004-02-05 13:49:08 +0100 |
---|---|---|
committer | justdave%syndicomm.com <> | 2004-02-05 13:49:08 +0100 |
commit | 11945a73c631bedbcf8daaba531964c3fc2d6333 (patch) | |
tree | 6c23288dd801bd8a1bf9ad548eb9a4e82cd24eef /docs/html/groups.html | |
parent | cfc778d1fc757e022c0755ccc5ecd430790ce8be (diff) | |
download | bugzilla-11945a73c631bedbcf8daaba531964c3fc2d6333.tar.gz bugzilla-11945a73c631bedbcf8daaba531964c3fc2d6333.tar.xz |
- 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.
Diffstat (limited to 'docs/html/groups.html')
-rw-r--r-- | docs/html/groups.html | 320 |
1 files changed, 0 insertions, 320 deletions
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 @@ -<HTML -><HEAD -><TITLE ->Groups and Group Security</TITLE -><META -NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ -"><LINK -REL="HOME" -TITLE="The Bugzilla Guide - 2.17.7 - Development Release" -HREF="index.html"><LINK -REL="UP" -TITLE="Administering Bugzilla" -HREF="administration.html"><LINK -REL="PREVIOUS" -TITLE="Voting" -HREF="voting.html"><LINK -REL="NEXT" -TITLE="Upgrading to New Releases" -HREF="upgrading.html"></HEAD -><BODY -CLASS="section" -BGCOLOR="#FFFFFF" -TEXT="#000000" -LINK="#0000FF" -VLINK="#840084" -ALINK="#0000FF" -><DIV -CLASS="NAVHEADER" -><TABLE -SUMMARY="Header navigation table" -WIDTH="100%" -BORDER="0" -CELLPADDING="0" -CELLSPACING="0" -><TR -><TH -COLSPAN="3" -ALIGN="center" ->The Bugzilla Guide - 2.17.7 - Development Release</TH -></TR -><TR -><TD -WIDTH="10%" -ALIGN="left" -VALIGN="bottom" -><A -HREF="voting.html" -ACCESSKEY="P" ->Prev</A -></TD -><TD -WIDTH="80%" -ALIGN="center" -VALIGN="bottom" ->Chapter 3. Administering Bugzilla</TD -><TD -WIDTH="10%" -ALIGN="right" -VALIGN="bottom" -><A -HREF="upgrading.html" -ACCESSKEY="N" ->Next</A -></TD -></TR -></TABLE -><HR -ALIGN="LEFT" -WIDTH="100%"></DIV -><DIV -CLASS="section" -><H1 -CLASS="section" -><A -NAME="groups" -></A ->3.8. Groups and Group Security</H1 -><P ->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 <SPAN -CLASS="QUOTE" ->"Edit Group Controls."</SPAN -> - </P -><P -> If the makeproductgroups param is on, a new group will be automatically - created for every new product. - </P -><P -> 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 -> For each group, it is possible to specify if membership in that - group is... - </P -><P -></P -><OL -TYPE="1" -><LI -><P -> required for bug entry, - </P -></LI -><LI -><P -> 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 -> 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 -> 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 <SPAN -CLASS="QUOTE" ->"Edit - Groups"</SPAN -> screen, then select the <SPAN -CLASS="QUOTE" ->"Add Group"</SPAN -> link.</P -></LI -><LI -><P ->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 <SPAN -CLASS="QUOTE" ->"Add"</SPAN ->.</P -><DIV -CLASS="warning" -><P -></P -><TABLE -CLASS="warning" -WIDTH="100%" -BORDER="0" -><TR -><TD -WIDTH="25" -ALIGN="CENTER" -VALIGN="TOP" -><IMG -SRC="../images/warning.gif" -HSPACE="5" -ALT="Warning"></TD -><TD -ALIGN="LEFT" -VALIGN="TOP" -><P ->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.</P -></TD -></TR -></TABLE -></DIV -></LI -><LI -><P ->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.</P -></LI -></OL -><P -> 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. 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 -CLASS="NAVFOOTER" -><HR -ALIGN="LEFT" -WIDTH="100%"><TABLE -SUMMARY="Footer navigation table" -WIDTH="100%" -BORDER="0" -CELLPADDING="0" -CELLSPACING="0" -><TR -><TD -WIDTH="33%" -ALIGN="left" -VALIGN="top" -><A -HREF="voting.html" -ACCESSKEY="P" ->Prev</A -></TD -><TD -WIDTH="34%" -ALIGN="center" -VALIGN="top" -><A -HREF="index.html" -ACCESSKEY="H" ->Home</A -></TD -><TD -WIDTH="33%" -ALIGN="right" -VALIGN="top" -><A -HREF="upgrading.html" -ACCESSKEY="N" ->Next</A -></TD -></TR -><TR -><TD -WIDTH="33%" -ALIGN="left" -VALIGN="top" ->Voting</TD -><TD -WIDTH="34%" -ALIGN="center" -VALIGN="top" -><A -HREF="administration.html" -ACCESSKEY="U" ->Up</A -></TD -><TD -WIDTH="33%" -ALIGN="right" -VALIGN="top" ->Upgrading to New Releases</TD -></TR -></TABLE -></DIV -></BODY -></HTML ->
\ No newline at end of file |