diff options
Diffstat (limited to 'docs/html/how.html')
| -rw-r--r-- | docs/html/how.html | 242 |
1 files changed, 121 insertions, 121 deletions
diff --git a/docs/html/how.html b/docs/html/how.html index cad748643..130674d1f 100644 --- a/docs/html/how.html +++ b/docs/html/how.html @@ -19,7 +19,7 @@ REL="NEXT" TITLE="Where can I find my user preferences?" HREF="init4me.html"></HEAD ><BODY -CLASS="SECTION" +CLASS="section" BGCOLOR="#FFFFFF" TEXT="#000000" LINK="#0000FF" @@ -66,11 +66,11 @@ HREF="init4me.html" ALIGN="LEFT" WIDTH="100%"></DIV ><DIV -CLASS="SECTION" +CLASS="section" ><H1 -CLASS="SECTION" +CLASS="section" ><A -NAME="HOW" +NAME="how" >2.3. How do I use Bugzilla?</A ></H1 ><TABLE @@ -97,7 +97,7 @@ VALIGN="TOP" ></TR ></TABLE ><P -> Bugzilla is a large, complex system. Describing how to use it +> Bugzilla is a large, complex system. Describing how to use it requires some time. If you are only interested in installing or administering a Bugzilla installation, please consult the Installing and Administering Bugzilla portions of this Guide. @@ -107,19 +107,19 @@ VALIGN="TOP" software. </P ><P -> Throughout this portion of the Guide, we will refer to user +> Throughout this portion of the Guide, we will refer to user account options available at the Bugzilla test installation, <A HREF="http://landfill.tequilarista.org/" TARGET="_top" -> landfill.tequilarista.org</A +> landfill.tequilarista.org</A >. <DIV -CLASS="NOTE" +CLASS="note" ><P ></P ><TABLE -CLASS="NOTE" +CLASS="note" WIDTH="100%" BORDER="0" ><TR @@ -135,7 +135,7 @@ ALT="Note"></TD ALIGN="LEFT" VALIGN="TOP" ><P -> Some people have run into difficulties completing this +> Some people have run into difficulties completing this tutorial. If you run into problems, please check the updated online documentation available at <A HREF="http://www.trilobyte.net/barnsons/" @@ -160,15 +160,15 @@ TARGET="_top" mentioned here. </P ><DIV -CLASS="SECTION" +CLASS="section" ><H2 -CLASS="SECTION" +CLASS="section" ><A -NAME="MYACCOUNT" +NAME="myaccount" >2.3.1. Create a Bugzilla Account</A ></H2 ><P -> First things first! If you want to use Bugzilla, first you +> First things first! If you want to use Bugzilla, first you need to create an account. Consult with the administrator responsible for your installation of Bugzilla for the URL you should use to access it. If you're test-driving the end-user @@ -184,19 +184,19 @@ TARGET="_top" TYPE="1" ><LI ><P -> Click the "Open a new Bugzilla account" link. +> Click the "Open a new Bugzilla account" link. </P ></LI ><LI ><P -> Enter your "E-mail address" and "Real Name" (or whatever +> Enter your "E-mail address" and "Real Name" (or whatever name you want to call yourself) in the spaces provided, then select the "Create Account" button. </P ></LI ><LI ><P -> 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 same as the email address), and a password you can use to access your account. This password is @@ -206,7 +206,7 @@ TYPE="1" ></LI ><LI ><P -> Click the <SPAN +> Click the <SPAN CLASS="QUOTE" >"Log In"</SPAN > link in the yellow area at @@ -224,12 +224,12 @@ CLASS="QUOTE" >"Login"</SPAN >. <DIV -CLASS="NOTE" +CLASS="note" ><P ></P ><TABLE -CLASS="NOTE" -WIDTH="90%" +CLASS="note" +WIDTH="100%" BORDER="0" ><TR ><TD @@ -244,7 +244,7 @@ ALT="Note"></TD ALIGN="LEFT" VALIGN="TOP" ><P -> If you ever forget your password, you can come back to +> If you ever forget your password, you can come back to this page, enter your <SPAN CLASS="QUOTE" >"E-mail address"</SPAN @@ -262,12 +262,12 @@ CLASS="QUOTE" ></DIV > <DIV -CLASS="CAUTION" +CLASS="caution" ><P ></P ><TABLE -CLASS="CAUTION" -WIDTH="90%" +CLASS="caution" +WIDTH="100%" BORDER="0" ><TR ><TD @@ -282,7 +282,7 @@ ALT="Caution"></TD ALIGN="LEFT" VALIGN="TOP" ><P -> Many modern browsers include an +> Many modern browsers include an <SPAN CLASS="QUOTE" >"Auto-Complete"</SPAN @@ -307,7 +307,7 @@ CLASS="QUOTE" ></LI ></OL ><P -> Congratulations! If you followed these directions, you now +> Congratulations! If you followed these directions, you now are the proud owner of a user account on landfill.tequilarista.org (Landfill) or your local Bugzilla install. You should now see in your browser a page called the @@ -319,46 +319,46 @@ CLASS="QUOTE" </P ></DIV ><DIV -CLASS="SECTION" +CLASS="section" ><H2 -CLASS="SECTION" +CLASS="section" ><A -NAME="QUERY" +NAME="query" >2.3.2. The Bugzilla Query Page</A ></H2 ><P -> The Bugzilla Query Page is the heart and soul of the Bugzilla +> The Bugzilla Query Page is the heart and soul of the Bugzilla user experience. It is the master interface where you can find any bug report, comment, or patch currently in the Bugzilla system. We'll go into how to create your own bug report later on. </P ><P -> There are efforts underway to simplify query usage. If you +> There are efforts underway to simplify query usage. If you have a local installation of Bugzilla 2.12 or higher, you should have <TT -CLASS="FILENAME" +CLASS="filename" >quicksearch.html</TT > available to use and simplify your searches. There is also a helper for the query interface, called <TT -CLASS="FILENAME" +CLASS="filename" >queryhelp.cgi</TT >. Landfill tends to run the latest code, so these two utilities should be available there for your perusal. </P ><P -> At this point, please visit the main Bugzilla site, +> At this point, let's visit the query page. <A -HREF="http://bugzilla.mozilla.org/query.cgi" +HREF="http://landfill.tequilarista.org/bugzilla-tip/query.cgi" TARGET="_top" -> bugzilla.mozilla.org</A ->, to see a more fleshed-out query page. +> landfill.tequilarista.org/bugzilla-tip/query.cgi</A +> </P ><P -> The first thing you need to notice about the Bugzilla Query +> The first thing you need to notice about the Bugzilla Query Page is that nearly every box you see on your screen has a hyperlink nearby, explaining what it is or what it does. Near the upper-left-hand corner of your browser window you should @@ -368,7 +368,7 @@ CLASS="QUOTE" > underlined. Select it. </P ><P -> Notice the page that popped up? Every underlined word you see +> Notice the page that popped up? Every underlined word you see on your screen is a hyperlink that will take you to context-sensitive help. Click around for a while, and learn what everything here does. To return to the query interface @@ -379,7 +379,7 @@ CLASS="QUOTE" button in your browser. </P ><P -> I'm sure that after checking out the online help, you are now +> I'm sure that after checking out the online help, you are now an expert on the Bugzilla Query Page. If, however, you feel you haven't mastered it yet, let me walk you through making a few successful queries to find out what there are in the @@ -391,7 +391,7 @@ CLASS="QUOTE" TYPE="1" ><LI ><P -> Ensure you are back on the <SPAN +> Ensure you are back on the <SPAN CLASS="QUOTE" >"Bugzilla Query Page"</SPAN @@ -407,7 +407,7 @@ CLASS="QUOTE" figured out. </P ><P -> Basically, selecting <EM +> Basically, selecting <EM >anything</EM > on the query page narrows your search down. Leaving stuff @@ -416,7 +416,7 @@ CLASS="QUOTE" ></LI ><LI ><P -> You see the box immediately below the top six boxes that +> You see the box immediately below the top six boxes that contains an "Email" text box, with the words "matching as", a drop-down selection box, then some checkboxes with "Assigned To" checked by default? This allows you to @@ -424,12 +424,12 @@ CLASS="QUOTE" put my email address in there, and see what happens. </P ><P -> Type "barnboy@trilobyte.net" in the top Email text box. +> Type "barnboy@trilobyte.net" in the top Email text box. </P ></LI ><LI ><P -> Let's narrow the search some more. Scroll down until you +> Let's narrow the search some more. Scroll down until you find the box with the word "Program" over the top of it. This is where we can narrow our search down to only specific products (software programs or product lines) in @@ -443,13 +443,13 @@ CLASS="QUOTE" ></LI ><LI ><P -> Did you notice that some of the boxes to the right changed +> Did you notice that some of the boxes to the right changed when you selected "Bugzilla"? Every Program (or Product) has different Versions, Components, and Target Milestones associated with it. A "Version" is the number of a software program. <DIV -CLASS="EXAMPLE" +CLASS="example" ><A NAME="AEN307" ></A @@ -458,14 +458,14 @@ NAME="AEN307" >Example 2-1. Some Famous Software Versions</B ></P ><DIV -CLASS="INFORMALEXAMPLE" +CLASS="informalexample" ><A NAME="AEN309" ></A ><P ></P ><P -> Do you remember the hype in 1995 when Microsoft +> Do you remember the hype in 1995 when Microsoft Windows 95(r) was released? It may have been several years ago, but Microsoft(tm) spent over $300 Million advertising this new Version of their software. @@ -475,7 +475,7 @@ NAME="AEN309" ME(Millenium Edition)(r). </P ><P -> Software "Versions" help a manufacturer +> Software "Versions" help a manufacturer differentiate their current product from their previous products. Most do not identify their products by the year they were released. Instead, @@ -492,7 +492,7 @@ NAME="AEN309" version than 1.1.1. </P ><P -> In general, a "Version" in Bugzilla should refer to +> In general, a "Version" in Bugzilla should refer to <EM >released</EM > products, not products @@ -507,13 +507,13 @@ NAME="AEN309" > </P ><P -> A "Component" is a piece of a Product. +> A "Component" is a piece of a Product. It may be a standalone program, or some other logical division of a Product or Program. Normally, a Component has a single Owner, who is responsible for overseeing efforts to improve that Component. <DIV -CLASS="EXAMPLE" +CLASS="example" ><A NAME="AEN317" ></A @@ -522,14 +522,14 @@ NAME="AEN317" >Example 2-2. Mozilla's Bugzilla Components</B ></P ><DIV -CLASS="INFORMALEXAMPLE" +CLASS="informalexample" ><A NAME="AEN319" ></A ><P ></P ><P -> Mozilla's "Bugzilla" Product is composed of several pieces (Components): +> Mozilla's "Bugzilla" Product is composed of several pieces (Components): <P ></P ><TABLE @@ -542,35 +542,35 @@ BORDER="0" >, Administration of a bugzilla installation, including <TT -CLASS="FILENAME" +CLASS="filename" >editcomponents.cgi</TT >, <TT -CLASS="FILENAME" +CLASS="filename" >editgroups.cgi</TT >, <TT -CLASS="FILENAME" +CLASS="filename" >editkeywords.cgi</TT >, <TT -CLASS="FILENAME" +CLASS="filename" >editparams.cgi</TT >, <TT -CLASS="FILENAME" +CLASS="filename" >editproducts.cgi</TT >, <TT -CLASS="FILENAME" +CLASS="filename" >editusers.cgi</TT >, <TT -CLASS="FILENAME" +CLASS="filename" >editversions.cgi,</TT > and <TT -CLASS="FILENAME" +CLASS="filename" >sanitycheck.cgi</TT >. </TD @@ -591,19 +591,19 @@ CLASS="FILENAME" >, Creating, changing, and viewing bugs. <TT -CLASS="FILENAME" +CLASS="filename" >enter_bug.cgi</TT >, <TT -CLASS="FILENAME" +CLASS="filename" >post_bug.cgi</TT >, <TT -CLASS="FILENAME" +CLASS="filename" >show_bug.cgi</TT > and <TT -CLASS="FILENAME" +CLASS="filename" >process_bug.cgi</TT >. </TD @@ -615,7 +615,7 @@ CLASS="FILENAME" >, The bugzilla documentation, including anything in the <TT -CLASS="FILENAME" +CLASS="filename" >docs/</TT > directory and The Bugzilla Guide (This document :) @@ -628,7 +628,7 @@ CLASS="FILENAME" >, Anything to do with email sent by Bugzilla. <TT -CLASS="FILENAME" +CLASS="filename" >processmail</TT > </TD @@ -640,7 +640,7 @@ CLASS="FILENAME" >, The installation process of Bugzilla. This includes <TT -CLASS="FILENAME" +CLASS="filename" >checksetup.pl</TT > and whatever else it evolves into. </TD @@ -652,11 +652,11 @@ CLASS="FILENAME" >, Anything to do with searching for bugs and viewing the buglists. <TT -CLASS="FILENAME" +CLASS="filename" >query.cgi</TT > and <TT -CLASS="FILENAME" +CLASS="filename" >buglist.cgi</TT > </TD @@ -668,11 +668,11 @@ CLASS="FILENAME" >, Getting reports from Bugzilla. <TT -CLASS="FILENAME" +CLASS="filename" >reports.cgi</TT > and <TT -CLASS="FILENAME" +CLASS="filename" >duplicates.cgi</TT > </TD @@ -684,7 +684,7 @@ CLASS="FILENAME" >, Anything about managing a user account from the user's perspective. <TT -CLASS="FILENAME" +CLASS="filename" >userprefs.cgi</TT >, saved queries, creating accounts, changing passwords, logging in, etc. @@ -712,7 +712,7 @@ CLASS="FILENAME" > </P ><P -> A "Milestone", or "Target Milestone" is a often a planned +> A "Milestone", or "Target Milestone" is a often a planned future "Version" of a product. In many cases, though, Milestones simply represent significant dates for a developer. Having certain features in your Product is @@ -727,7 +727,7 @@ CLASS="FILENAME" of reach by the time the important day arrives. </P ><P -> The Bugzilla Project has set up Milestones for future +> The Bugzilla Project has set up Milestones for future Bugzilla versions 2.14, 2.16, 2.18, 3.0, etc. However, a Target Milestone can just as easily be a specific date, code name, or weird alphanumeric combination, like "M19". @@ -735,19 +735,19 @@ CLASS="FILENAME" ></LI ><LI ><P -> OK, now let's select the "Bugzilla" component from its scrollbox. +> OK, now let's select the "Bugzilla" component from its scrollbox. </P ></LI ><LI ><P -> Skip down the page a bit -- do you see the "submit query" button? +> Skip down the page a bit -- do you see the "submit query" button? Select it, and let's run this query! </P ></LI ><LI ><P -> Congratulations! You've completed your first Query, and +> Congratulations! You've completed your first Query, and have before you the Bug List of the author of this Guide, Matthew P. Barnson (barnboy@trilobyte.net). If I'm doing well, you'll have a cryptic "Zarro Boogs Found" message on @@ -759,7 +759,7 @@ CLASS="FILENAME" ></LI ></OL ><P -> I encourage you to click the bug numbers in the left-hand +> I encourage you to click the bug numbers in the left-hand column and examine my bugs. Also notice that if you click the underlined links near the top of this page, they do not take you to context-sensitive help here, but instead sort the @@ -768,7 +768,7 @@ CLASS="FILENAME" this is a tremendous timesaver. </P ><P -> A couple more interesting things about the Bug List page: +> A couple more interesting things about the Bug List page: <P ></P ><TABLE @@ -817,11 +817,11 @@ BORDER="0" > </P ><DIV -CLASS="NOTE" +CLASS="note" ><P ></P ><TABLE -CLASS="NOTE" +CLASS="note" WIDTH="100%" BORDER="0" ><TR @@ -837,7 +837,7 @@ ALT="Note"></TD ALIGN="LEFT" VALIGN="TOP" ><P -> There are many more options to the Bugzilla Query Page and +> There are many more options to the Bugzilla Query Page and the Bug List than I have shown you. But this should be enough for you to learn to get around. I encourage you to check out the <A @@ -852,11 +852,11 @@ TARGET="_top" ></DIV ></DIV ><DIV -CLASS="SECTION" +CLASS="section" ><H2 -CLASS="SECTION" +CLASS="section" ><A -NAME="BUGREPORTS" +NAME="bugreports" >2.3.3. Creating and Managing Bug Reports</A ></H2 ><TABLE @@ -885,15 +885,15 @@ VALIGN="TOP" ></TR ></TABLE ><DIV -CLASS="SECTION" +CLASS="section" ><H3 -CLASS="SECTION" +CLASS="section" ><A -NAME="BUG_WRITING" +NAME="bug-writing" >2.3.3.1. Writing a Great Bug Report</A ></H3 ><P -> Before we plunge into writing your first bug report, I +> Before we plunge into writing your first bug report, I encourage you to read some bug-writing guidelines. If you are reading this document as part of a Bugzilla CVS checkout or un-tarred Bugzilla distribution, you should be able to @@ -908,7 +908,7 @@ TARGET="_top" >. 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. </P ><P -> While you are at it, why not learn how to find previously +> While you are at it, why not learn how to find previously reported bugs? Mozilla.org has published a great tutorial on finding duplicate bugs, available at <A HREF="http://www.mozilla.org/quality/help/beginning-duplicate-finding.html" @@ -917,7 +917,7 @@ TARGET="_top" >. </P ><P -> I realize this was a lot to read. However, understanding +> I realize this was a lot to read. However, understanding the mentality of writing great bug reports will help us on the next part! </P @@ -927,7 +927,7 @@ TARGET="_top" TYPE="1" ><LI ><P -> Go back to <A +> Go back to <A HREF="http://landfill.tequilarista.org/bugzilla-tip/" TARGET="_top" > http://landfill.tequilarista.org/bugzilla-tip/</A @@ -936,7 +936,7 @@ TARGET="_top" ></LI ><LI ><P -> Select the <A +> Select the <A HREF="http://landfill.tequilarista.org/bugzilla-tip/enter_bug.cgi" TARGET="_top" > Enter a new bug report</A @@ -945,12 +945,12 @@ TARGET="_top" ></LI ><LI ><P -> Select a product. +> Select a product. </P ></LI ><LI ><P -> Now you should be at the "Enter Bug" form. The +> Now you should be at the "Enter Bug" form. The "reporter" should have been automatically filled out for you (or else Bugzilla prompted you to Log In again -- you did keep the email with your username and password, @@ -959,12 +959,12 @@ TARGET="_top" ></LI ><LI ><P -> Select a Component in the scrollbox. +> Select a Component in the scrollbox. </P ></LI ><LI ><P -> Bugzilla should have made reasonable guesses, based upon +> Bugzilla should have made reasonable guesses, based upon your browser, for the "Platform" and "OS" drop-down boxes. If those are wrong, change them -- if you're on an SGI box running IRIX, we want to know! @@ -972,7 +972,7 @@ TARGET="_top" ></LI ><LI ><P -> Fill in the "Assigned To" box with the email address you +> Fill in the "Assigned To" box with the email address you provided earlier. This way you don't end up sending copies of your bug to lots of other people, since it's just a test bug. @@ -980,33 +980,33 @@ TARGET="_top" ></LI ><LI ><P -> Leave the "CC" text box blank. Fill in the "URL" box +> Leave the "CC" text box blank. Fill in the "URL" box with "http://www.mozilla.org". </P ></LI ><LI ><P -> Enter "The Bugzilla Guide" in the Summary text box, and +> Enter "The Bugzilla Guide" in the Summary text box, and place any comments you have on this tutorial, or the Guide in general, into the Description box. </P ></LI ></OL ><P -> Voila! Select "Commit" and send in your bug report! Next +> Voila! Select "Commit" and send in your bug report! Next we'll look at resolving bugs. </P ></DIV ><DIV -CLASS="SECTION" +CLASS="section" ><H3 -CLASS="SECTION" +CLASS="section" ><A -NAME="BUG_MANAGE" +NAME="bug-manage" >2.3.3.2. Managing your Bug Reports</A ></H3 ><P -> OK, you should have a link to the bug you just created near +> OK, you should have a link to the bug you just created near the top of your page. It should say "Bug XXXX posted", with a link to the right saying "Back to BUG# XXXX". Select this link. @@ -1017,7 +1017,7 @@ NAME="BUG_MANAGE" TYPE="1" ><LI ><P -> Scroll down a bit on the subsequent page, until you see +> Scroll down a bit on the subsequent page, until you see the "Resolve bug, changing resolution to (dropdown box). Normally, you would "Accept bug (change status to ASSIGNED)", fix it, and then resolve. But in this case, @@ -1029,7 +1029,7 @@ TYPE="1" ></LI ><LI ><P -> Hey! It said it couldn't take the change in a big red +> Hey! It said it couldn't take the change in a big red box! That's right, you must specify a Comment in order to make this change. Select the "Back" button in your browser, add a Comment, then try Resolving the bug with @@ -1038,40 +1038,40 @@ TYPE="1" ></LI ></OL ><P -> You have now learned the basics of Bugzilla navigation, +> You have now learned the basics of Bugzilla navigation, entering a bug, and bug maintenance. I encourage you to explore these features, and see what you can do with them! We'll spend no more time on individual Bugs or Queries from this point on, so you are on your own there. </P ><P -> But I'll give a few last hints! +> But I'll give a few last hints! </P ><P -> There is a <A -HREF="http://bugzilla.mozilla.org/help.html" +> There is a <A +HREF="http://landfill.tequilarista.org/bugzilla-tip/help.html" TARGET="_top" >CLUE</A > on the Query page that will teach you more how to use the form. </P ><P -> If you click the hyperlink on the <A -HREF="http://bugzilla.mozilla.org/describecomponents.cgi" +> If you click the hyperlink on the <A +HREF="http://landfill.tequilarista.org/bugzilla-tip/describecomponents.cgi" TARGET="_top" >Component</A > box of the Query page, you will be presented a form that will describe what all the components are. </P ><P -> Possibly the most powerful feature of the Query page is the +> Possibly the most powerful feature of the Query page is the <A -HREF="http://bugzilla.mozilla.org/booleanchart.html" +HREF="http://landfill.tequilarista.org/bugzilla-tip/booleanchart.html" TARGET="_top" >Boolean Chart</A > section. It's a bit confusing to use the first time, but can provide unparalleled flexibility in your queries, allowing you to build extremely powerful requests. </P ><P -> Finally, you can build some nifty <A -HREF="http://bugzilla.mozilla.org/reports.cgi" +> Finally, you can build some nifty <A +HREF="http://landfill.tequilarista.org/bugzilla-tip/reports.cgi" TARGET="_top" >Reports</A > using the "Bug Reports" link near the bottom of the query page, and also available via the "Reports" link at the footer of each page. |