From d7f381254270028c7d239463521005f576575151 Mon Sep 17 00:00:00 2001 From: "jake%acutex.net" <> Date: Sat, 19 Jan 2002 07:26:39 +0000 Subject: Latest version of compiled docs (picking up recent SGML changes). --- docs/html/programadmin.html | 279 ++++++++++++++++++++++---------------------- 1 file changed, 140 insertions(+), 139 deletions(-) (limited to 'docs/html/programadmin.html') diff --git a/docs/html/programadmin.html b/docs/html/programadmin.html index ea2bcbcfc..b4e3bca3d 100644 --- a/docs/html/programadmin.html +++ b/docs/html/programadmin.html @@ -20,7 +20,7 @@ REL="NEXT" TITLE="Bugzilla Security" HREF="security.html">
Products are @@ -124,7 +124,7 @@ CLASS="GLOSSTERM" products (website, meetings...)
A Product (formerly called "Program", and still referred to +> A Product (formerly called "Program", and still referred to that way in some portions of the source code) controls some very important functions. The number of "votes" available for users to vote for the most important bugs is set per-product, @@ -141,15 +141,15 @@ CLASS="GLOSSTERM" TYPE="1" >
Select "components" from the yellow footer +> Select "components" from the yellow footer
To create new Milestones, set Default Milestones, and set +> To create new Milestones, set Default Milestones, and set Milestone URL:
Select "edit milestones" +> Select "edit milestones"
Select "Add" to the right of the "Add a new milestone" +> Select "Add" to the right of the "Add a new milestone" text
Enter the name of the Milestone in the "Milestone" field. +> Enter the name of the Milestone in the "Milestone" field. You can optionally set the "Sortkey", which is a positive or negative number (-255 to 255) that defines where in the list this particular milestone appears. Select "Add".
Example 4-4. Using SortKey with Target Milestone
Let's say you create a target milestone called +> Let's say you create a target milestone called "Release 1.0", with Sortkey set to "0". Later, you realize that you will have a public beta, called "Beta1". You can create a Milestone called "Beta1", @@ -593,17 +593,17 @@ NAME="AEN1524" >
If you want to add more milestones, select the "Edit" +> If you want to add more milestones, select the "Edit" link. If you don't, well shoot, you have to go back to the "query" page and select "components" again, and make your way back to the Product you were editing.
To enable Generic Group Security ("usebuggroups"): +> To enable Generic Group Security ("usebuggroups"):
Turn "On" "usebuggroups" in the "Edit Parameters" screen. +> Turn "On" "usebuggroups" in the "Edit Parameters" screen.
You will generally have no groups set up. Select the +> You will generally have no groups set up. Select the "groups" link in the footer.
Take a moment to understand the instructions on the "Edit +> Take a moment to understand the instructions on the "Edit Groups" screen. Once you feel confident you understand what is expected of you, select the "Add Group" link.
Fill out the "New Name" (remember, no spaces!), "New +> Fill out the "New Name" (remember, no spaces!), "New Description", and "New User RegExp" fields. "New User RegExp" allows you to automatically place all users who fulfill the Regular Expression into the new group.
Example 4-6. Creating a New Group
I created a group called DefaultGroup with a
+>
I created a group called DefaultGroup with a
description of "This is simply a group to play
@@ -950,14 +950,14 @@ CLASS="QUOTE"
> To enable Product-Based Group Security (usebuggroupsentry):
+>
To enable Product-Based Group Security (usebuggroupsentry):
Don't forget that you only have 64 groups masks available,
+>
Don't forget that you only have 64 groups masks available,
total, for your installation of Bugzilla! If you plan on
having more than 50 products in your individual Bugzilla
installation, and require group security for your products,
@@ -991,16 +991,16 @@ VALIGN="TOP"
TYPE="1"
> Turn "On" "usebuggroups" and "usebuggroupsentry" in the
+>
Turn "On" "usebuggroups" and "usebuggroupsentry" in the
"Edit Parameters" screen.
"usebuggroupsentry" has the capacity to prevent the
+>
"usebuggroupsentry" has the capacity to prevent the
administrative user from directly altering bugs because
of conflicting group permissions. If you plan on using
"usebuggroupsentry", you should plan on restricting
@@ -1031,7 +1031,7 @@ VALIGN="TOP"
> You will generally have no Groups set up, unless you
+>
You will generally have no Groups set up, unless you
enabled "usebuggroupsentry" prior to creating any
Products. To create "Generic Group Security" groups,
follow the instructions given above. To create
@@ -1044,19 +1044,20 @@ VALIGN="TOP"
> You may find this example illustrative for how bug groups work.
+>
You may find this example illustrative for how bug groups work.