<entry><foreignphrase>Prompt</foreignphrase> of users command under bash shell</entry>
<entry>
<foreignphrase>Prompt</foreignphrase>
of users command under bash shell</entry>
<entry>bash$</entry>
<entry>bash$</entry>
</row>
</row>
<row>
<row>
<entry><foreignphrase>Prompt</foreignphrase> of root users command under bash shell</entry>
<entry>
<foreignphrase>Prompt</foreignphrase>
of root users command under bash shell</entry>
<entry>bash#</entry>
<entry>bash#</entry>
</row>
</row>
<row>
<row>
<entry><foreignphrase>Prompt</foreignphrase> of user command under tcsh shell</entry>
<entry>
<foreignphrase>Prompt</foreignphrase>
of user command under tcsh shell</entry>
<entry>tcsh$</entry>
<entry>tcsh$</entry>
</row>
</row>
<row>
<row>
<entry>Environment Variables</entry>
<entry>Environment Variables</entry>
<entry><envar>VARIABLE</envar></entry>
<entry>
<envar>VARIABLE</envar>
</entry>
</row>
</row>
<row>
<row>
<entry>Emphasized word</entry>
<entry>Emphasized word</entry>
<entry><emphasis>word</emphasis></entry>
<entry>
<emphasis>word</emphasis>
</entry>
</row>
</row>
<row>
<row>
<entry>Code Example</entry>
<entry>Code Example</entry>
<entry><programlisting><sgmltagclass="starttag">para</sgmltag>Beginning and end of paragraph<sgmltagclass="endtag">para</sgmltag></programlisting></entry>
Click the <quote>Open a new Bugzilla account</quote> link, enter your
<quote>Open a new Bugzilla account</quote>
email address and, optionally, your name in the spaces provided,
then click <quote>Create Account</quote>.
link, enter your email address and, optionally, your name in the
</para>
spaces provided, then click
<quote>Create Account</quote>
.</para>
</listitem>
</listitem>
<listitem>
<listitem>
<para>
<para>Within moments, you should receive an email to the address
Within moments, you should receive an email to the address
you provided above, which contains your login name (generally the
you provided above, which contains your login name
same as the email address), and a password you can use to access
(generally the same as the email address), and a password
your account. This password is randomly generated, and can be
you can use to access your account. This password is
changed to something more memorable.</para>
randomly generated, and can be changed to something more memorable.
</para>
</listitem>
</listitem>
<listitem>
<listitem>
<para>
<para>Click the
Click the <quote>Log In</quote> link in the yellow area at
<quote>Log In</quote>
the bottom of the page in your browser, enter your
email address and password into the spaces provided, and click
link in the yellow area at the bottom of the page in your browser,
<quote>Login</quote>.
enter your email address and password into the spaces provided, and
</para>
click
<quote>Login</quote>
.</para>
</listitem>
</listitem>
</orderedlist>
</orderedlist>
<para>
You are now logged in. Bugzilla uses cookies for authentication, so
<para>You are now logged in. Bugzilla uses cookies for authentication,
(unless your IP address changes) you should not have to log in again.
so (unless your IP address changes) you should not have to log in
</para>
again.</para>
</section>
</section>
<sectionid="bug_page">
<sectionid="bug_page">
<title>Anatomy of a Bug</title>
<title>Anatomy of a Bug</title>
<para>
The core of Bugzilla is the screen which displays a particular bug.
<para>The core of Bugzilla is the screen which displays a particular
It's a good place to explain some Bugzilla concepts.
bug. It's a good place to explain some Bugzilla concepts.
<ulinkurl="http://landfill.tequilarista.org/bugzilla-tip/show_bug.cgi?id=1">Bug 1 on Landfill</ulink> is a good example. Note that the names of most fields
<ulink
are hyperlinks; clicking them will take you to context-sensitive
While some of the advice is Mozilla-specific, the basic principles of reporting Reproducible, Specific bugs, isolating the Product you are using, the Version of the Product, the Component which failed, the Hardware Platform, and Operating System you were using at the time of the failure go a long way toward ensuring accurate, responsible fixes for the bug that bit you.
Bug Writing Guidelines</ulink>
</para>
<para>
. While some of the advice is Mozilla-specific, the basic principles of
The procedure for filing a test bug is as follows:
reporting Reproducible, Specific bugs, isolating the Product you are
</para>
using, the Version of the Product, the Component which failed, the
Hardware Platform, and Operating System you were using at the time of
the failure go a long way toward ensuring accurate, responsible fixes
for the bug that bit you.</para>
<para>The procedure for filing a test bug is as follows:</para>
On this page, you can change your basic Account Settings,
<para>On this tab, you can change your basic Account Settings,
including your password and full name. For security reasons,
including your password, email address and real name. For security
in order to change anything on this page you must type your
reasons, in order to change anything on this page you must type your
<emphasis>current</emphasis> password into the <quote>Old
<emphasis>current</emphasis>
Password</quote> field. If you wish to change your
password, type the new password you want into the <quote>New
password into the
Password</quote> field and again into the <quote>Re-enter
<quote>Password</quote>
new password</quote> field to ensure you typed your new
password correctly. Select the <quote>Submit</quote> button
field. If you attempt to change your email address, a confirmation
and you are done.
email is sent to both the old and new addresses, with a link to use to
</para>
confirm the change. This helps to prevent account hijacking.</para>
</section>
</section>
<sectionid="emailsettings">
<sectionid="emailsettings">
<title>Email Settings</title>
<title>Email Settings</title>
<sectionid="notification"xreflabel="">
<title>Email Notification</title>
<para>On this tab you can reduce or increase the amount of email sent
<para>
you from Bugzilla, opting in our out depending on your relationship to
Here you can reduce or increase the amount of email sent you
the bug and the change that was made to it. (Note that you can also do
from Bugzilla. Although this is referred to as
client-side filtering using the X-Bugzilla-Reason header which Bugzilla
<quote>Advanced Email Filtering Options</quote>, they are,
adds to all bugmail.)</para>
in fact, the standard email filter set. All of them are
self-explanatory, but you can use the filters in interesting
<para>By entering user email names, delineated by commas, into the
ways. For instance, some people (notably Quality Assurance
"Users to watch" text entry box you can receive a copy of all the
personnel) often only care to receive updates regarding a
bugmail of other users (security settings permitting.) This powerful
bug when the bug changes state, so they can track bugs on
functionality enables seamless transitions as developers change
their flow charts and know when it is time to pull the bug
projects, managers wish to get in touch with the issues faced by their
onto a quality assurance platform for inspection. Other
direct reports, or users go on vacation.</para>
people set up email gateways to
<xreflinkend="bonsai"/> or <xreflinkend="tinderbox"/>, and
restrict which types of Bugzilla information are fed to
these systems..
</para>
</section>
<sectionid="newemailtech">
<title>New Email Technology</title>
<note>
<para>
This option may not be available in all Bugzilla
installations, depending upon the preferences of the
systems administrator responsible for the setup of your
Bugzilla. However, if you really want this functionality,
ask her to "enable newemailtech in Params" and "make it
the default for all new users", referring her to the
Administration section of this Guide.
</para>
</note>
<para>
Disregard the warnings about "experimental and bleeding
edge"; the code to handle email in a cleaner manner than
that historically used for Bugzilla is quite robust and
well-tested now.
</para>
<para>
I recommend you enable the option, "Click here to sign up
(and risk any bugs)". Your email-box will thank you for it.
The fundamental shift in "newemailtech" is away from
standard UNIX "diff" output, which is quite ugly, to a
prettier, better laid-out email.
</para>
</section>
<sectionid="watchsettings">
<title>"Watching" Users</title>
<note>
<note>
<para>
<para>This option may not be available in all Bugzilla installations.
This option may not be available in all Bugzilla
Ask your administrator.</para>
installations, depending upon the preferences of the
systems administrator responsible for the setup of your
Bugzilla. However, if you really want this functionality,
ask her to "enable watchers in Params".
</para>
</note>
</note>
<para>
By entering user email names into the "Users to watch" text
entry box, delineated by commas, you can watch bugs of other
users. This powerful functionality enables seamless
transitions as developers change projects, managers wish to
get in touch with the issues faced by their direct reports,
or users go on vacation. If any of these three situations
apply to you, you will undoubtedly find this feature quite
convenient.
</para>
</section>
</section>
</section>
<sectionid="footersettings">
<sectionid="footersettings">
<title>Page Footer</title>
<title>Page Footer</title>
<note>
<para>
<para>By default, this page is quite barren. However, if you explore
By default, this page is quite barren. However, go explore
the Search page some more, you will find that you can store numerous
the Query Page some more; you will find that you can store
queries on the server, so if you regularly run a particular query it is
numerous queries on the server, so if you regularly run a
just a drop-down menu away. Once you have a stored query, you can come
particular query it is just a drop-down menu away. On this
here to request that it also be displayed in your page footer.</para>
page of Preferences, if you have many stored queries you can
elect to have them always one-click away!
</para>
</note>
<para>
If you have many stored queries on the server, here you will
find individual drop-downs for each stored query. Each
drop-down gives you the option of that query appearing on the
footer of every page in Bugzilla! This gives you powerful
one-click access to any complex searches you may set up, and
is an excellent way to impress your boss...
</para>
<tip>
<para>By default, the "My Bugs" link appears at the bottom of
each page. However, this query gives you both the bugs you
have reported, as well as those you are assigned. One of
the most common uses for this page is to remove the "My
Bugs" link, replacing it with two other queries, commonly
called "My Bug Reports" and "My Bugs" (but only referencing
bugs assigned to you). This allows you to distinguish those
bugs you have reported from those you are assigned. I
commonly set up complex Boolean queries in the Query page
and link them to my footer in this page. When they are
significantly complex, a one-click reference can save hours
of work.</para>
</tip>
</section>
</section>
<sectionid="permissionsettings">
<sectionid="permissionsettings">
<title>Permissions</title>
<title>Permissions</title>
<para>
This is a purely informative page which outlines your current
permissions on this installation of Bugzilla. If you have
permissions to grant certain permissions to other users, the
"other users" link appears on this page as well as the footer.
For more information regarding user administration, please
consult the Administration section of this Guide.
</para>
</section>
</section>
<sectionid="usingbz-conc">
<para>This is a purely informative page which outlines your current
<title>Using Bugzilla-Conclusion</title>
permissions on this installation of Bugzilla - what product groups you
<para>
are in, and whether you can edit bugs or perform various administration
Thank you for reading through this portion of the Bugzilla
functions.</para>
Guide. I anticipate it may not yet meet the needs of all
</section>
readers. If you have additional comments or corrections to
make, please submit your contributions to the <ulink
url="mailto://mozilla-webtools@mozilla.org">mozilla-webtools</ulink> mailing list/newsgroup. The mailing list is mirrored to the netscape.public.mozilla.webtools newsgroup, and the newsgroup is mirrored to mozilla-webtools@mozilla.org
