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/useradmin.html | 179 ++++++++++++++++++++++++----------------------- 1 file changed, 90 insertions(+), 89 deletions(-) (limited to 'docs/html/useradmin.html') diff --git a/docs/html/useradmin.html b/docs/html/useradmin.html index a57ed8bbb..b2e8fd7cb 100644 --- a/docs/html/useradmin.html +++ b/docs/html/useradmin.html @@ -20,7 +20,7 @@ TITLE="Product, Component, Milestone, and Version Administration" HREF="programadmin.html">

4.2. User Administration

User administration is one of the easiest parts of Bugzilla. +> User administration is one of the easiest parts of Bugzilla. Keeping it from getting out of hand, however, can become a challenge.

4.2.1. Creating the Default User

When you first run checksetup.pl after installing Bugzilla, it +> When you first run checksetup.pl after installing Bugzilla, it will prompt you for the administrative username (email address) and password for this "super user". If for some reason you were to delete the "super user" account, re-running @@ -96,11 +96,11 @@ NAME="DEFAULTUSER" password.

If you wish to add more administrative users, you must use the +> If you wish to add more administrative users, you must use the MySQL interface. Run "mysql" from the command line, and use these commands ("mysql>" denotes the mysql prompt, not something you should type in): mysql> use bugs; mysql> update profiles set groupset=0x7ffffffffffffff where login_name = "(user's @@ -152,19 +152,19 @@ CLASS="QUOTE" >

4.2.2. Managing Other Users

4.2.2.1. Logging In

  • Open the index.html page for your Bugzilla installation +> Open the index.html page for your Bugzilla installation in your browser window.

  • Click the "Query Existing Bug Reports" link. +> Click the "Query Existing Bug Reports" link.

  • Click the "Log In" link at the foot of the page. +> Click the "Log In" link at the foot of the page.

  • Type your email address, and the password which was +> Type your email address, and the password which was emailed to you when you created your Bugzilla account, into the spaces provided.

    Congratulations, you are logged in!

  • 4.2.2.2. Creating new users

    Your users can create their own user accounts by clicking +> Your users can create their own user accounts by clicking the "New Account" link at the bottom of each page. However, should you desire to create user accounts ahead of time, here is how you do it. @@ -218,24 +218,24 @@ NAME="CREATENEWUSERS" TYPE="1" >

  • After logging in, click the "Users" link at the footer +> After logging in, click the "Users" link at the footer of the query page.

  • To see a specific user, type a portion of their login +> To see a specific user, type a portion of their login name in the box provided and click "submit". To see all users, simply click the "submit" button. You must click "submit" here to be able to add a new user.

  • More functionality is available via the list on the +> More functionality is available via the list on the right-hand side of the text entry box. You can match what you type as a case-insensitive substring (the default) of all users on your system, a case-sensitive regular expression (please see the man regexp manual page for details on regular @@ -272,22 +272,22 @@ CLASS="COMMAND" >

  • Click the "Add New User" link at the bottom of the user +> Click the "Add New User" link at the bottom of the user list

  • Fill out the form presented. This page is +> Fill out the form presented. This page is self-explanatory. When done, click "submit".

  • Adding a user this way will Adding a user this way will not send an email informing them of their username and @@ -326,15 +326,15 @@ CLASS="QUOTE" >

    4.2.2.3. Disabling Users

    I bet you noticed that big "Disabled Text" entry box +> I bet you noticed that big "Disabled Text" entry box available from the "Add New User" screen, when you edit an account? By entering any text in this box and selecting "submit", you have prevented the user from using Bugzilla @@ -342,11 +342,11 @@ NAME="DISABLEUSERS" text box, will be presented to the user the next time she attempts to use the system.

    Don't disable your own administrative account, or you +> Don't disable your own administrative account, or you will hate life!

    4.2.2.4. Modifying Users

    Here I will attempt to describe the function of each option +> Here I will attempt to describe the function of each option on the Edit User screen.

    • Login Name: This is generally the user's email address. However, if you have edited your system parameters, this may just be the user's login name or some other identifier.

    For compatability reasons, you should probably stick +> For compatability reasons, you should probably stick with email addresses as user login names. It will make your life easier.

  • Real Name: Duh!

  • Password: You can change the user password here. It is normal to only see asterisks. @@ -453,7 +453,7 @@ VALIGN="TOP" >

  • Email Notification: You may choose from one of three options: @@ -463,7 +463,7 @@ VALIGN="TOP" TYPE="1" >

  • All qualifying bugs except those which I change: +> All qualifying bugs except those which I change: The user will be notified of any change to any bug for which she is the reporter, assignee, QA Contact, CC recipient, or "watcher". @@ -471,18 +471,18 @@ TYPE="1" >

  • Only those bugs which I am listed on the CC line: +> Only those bugs which I am listed on the CC line: The user will not be notified of changes to bugs where she is the assignee, reporter, or QA Contact, but will receive them if she is on the CC list.

  • She will still receive whining cron emails if +> She will still receive whining cron emails if you set up the "whinemail" feature.

  • All Qualifying Bugs: This user is a glutton for punishment. If her name is @@ -519,9 +519,10 @@ VALIGN="TOP"

  • +

    Disable Text: If you type anything in this box, including just a space, the user account is @@ -529,12 +530,12 @@ VALIGN="TOP" interface, and what you type in this box is presented as the reason.

    As of this writing, the user can still submit bugs +> As of this writing, the user can still submit bugs via the e-mail gateway, if you set it up, despite the disabled text field. The e-mail gateway should

  • CanConfirm: This field is only used if you have enabled "unconfirmed" status in your @@ -606,7 +607,7 @@ VALIGN="TOP" >

  • Creategroups: This option will allow a user to create and destroy groups in Bugzilla. @@ -617,18 +618,18 @@ VALIGN="TOP" >

  • Editbugs: Unless a user has this bit set, they can only edit those bugs for which they are the assignee or the reporter.

  • Leaving this option unchecked does not prevent users +> Leaving this option unchecked does not prevent users from adding comments to a bug! They simply cannot change a bug priority, severity, etc. unless they are the assignee or reporter. @@ -657,7 +658,7 @@ VALIGN="TOP" >

  • Editcomponents: This flag allows a user to create new products and components, as well as @@ -673,7 +674,7 @@ VALIGN="TOP" >

  • Editkeywords: If you use Bugzilla's keyword functionality, enabling this feature allows a @@ -690,7 +691,7 @@ VALIGN="TOP" >

  • Editusers: This flag allows a user do what you're doing right now: edit other users. This @@ -701,7 +702,7 @@ VALIGN="TOP" >

  • PRODUCT: PRODUCT bugs access. This allows an administrator, with product-level granularity, -- cgit v1.2.3-24-g4f1b