1
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
5
>How do I use Bugzilla?</TITLE
8
CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
10
TITLE="The Bugzilla Guide - 2.16.7 Release"
11
HREF="index.html"><LINK
13
TITLE="Using Bugzilla"
14
HREF="using.html"><LINK
16
TITLE="Using Bugzilla"
17
HREF="using.html"><LINK
19
TITLE="Hints and Tips"
20
HREF="hintsandtips.html"></HEAD
31
SUMMARY="Header navigation table"
40
>The Bugzilla Guide - 2.16.7 Release</TH
56
>Chapter 3. Using Bugzilla</TD
62
HREF="hintsandtips.html"
77
>3.1. How do I use Bugzilla?</A
80
>This section contains information for end-users of Bugzilla. There
81
is a Bugzilla test installation, called
83
HREF="http://landfill.bugzilla.org/"
87
welcome to play with (if it's up). However, not all of the Bugzilla
88
installations there will necessarily have all Bugzilla features enabled,
89
and different installations run different versions, so some things may not
90
quite work as this document describes.</P
97
>3.1.1. Create a Bugzilla Account</A
100
>If you want to use Bugzilla, first you need to create an account.
101
Consult with the administrator responsible for your installation of
102
Bugzilla for the URL you should use to access it. If you're
103
test-driving Bugzilla, use this URL:
105
HREF="http://landfill.bugzilla.org/bugzilla-2.16.7/"
107
>http://landfill.bugzilla.org/bugzilla-2.16.7/</A
119
>"Open a new Bugzilla account"</SPAN
122
link, enter your email address and, optionally, your name in the
123
spaces provided, then click
126
>"Create Account"</SPAN
133
>Within moments, you should receive an email to the address
134
you provided above, which contains your login name (generally the
135
same as the email address), and a password you can use to access
136
your account. This password is randomly generated, and can be
137
changed to something more memorable.</P
146
link in the yellow area at the bottom of the page in your browser,
147
enter your email address and password into the spaces provided, and
157
>You are now logged in. Bugzilla uses cookies for authentication
158
so, unless your IP address changes, you should not have to log in
167
>3.1.2. Anatomy of a Bug</A
170
>The core of Bugzilla is the screen which displays a particular
171
bug. It's a good place to explain some Bugzilla concepts.
173
HREF="http://landfill.bugzilla.org/bugzilla-2.16.7/show_bug.cgi?id=1"
175
> Bug 1 on Landfill</A
178
is a good example. Note that the labels for most fields are hyperlinks;
179
clicking them will take you to context-sensitive help on that
180
particular field. Fields marked * may not be present on every
181
installation of Bugzilla.</P
189
>Product and Component</EM
191
Bugs are divided up by Product and Component, with a Product
192
having one or more Components in it. For example,
193
bugzilla.mozilla.org's "Bugzilla" Product is composed of several
205
Administration of a Bugzilla installation.</TD
210
>Bugzilla-General:</EM
212
Anything that doesn't fit in the other components, or spans
213
multiple components.</TD
218
>Creating/Changing Bugs:</EM
220
Creating, changing, and viewing bugs.</TD
227
The Bugzilla documentation, including The Bugzilla Guide.</TD
234
Anything to do with email sent by Bugzilla.</TD
241
The installation process of Bugzilla.</TD
248
Anything to do with searching for bugs and viewing the
254
>Reporting/Charting:</EM
256
Getting reports from Bugzilla.</TD
263
Anything about managing a user account from the user's perspective.
264
Saved queries, creating accounts, changing passwords, logging in,
272
General issues having to do with the user interface cosmetics (not
273
functionality) including cosmetic issues, HTML templates,
286
>Status and Resolution:</EM
289
These define exactly what state the bug is in - from not even
290
being confirmed as a bug, through to being fixed and the fix
291
confirmed by Quality Assurance. The different possible values for
292
Status and Resolution on your installation should be documented in the
293
context-sensitive help for those items.</P
300
The person responsible for fixing the bug.</P
307
A URL associated with the bug, if any.</P
314
A one-sentence summary of the problem.</P
319
>*Status Whiteboard:</EM
321
(a.k.a. Whiteboard) A free-form text area for adding short notes
322
and tags to a bug.</P
329
The administrator can define keywords which you can use to tag and
330
categorise bugs - e.g. The Mozilla Project has keywords like crash
336
>Platform and OS:</EM
338
These indicate the computing environment where the bug was
346
The "Version" field is usually used for versions of a product which
347
have been released, and is set to indicate which versions of a
348
Component have the particular problem the bug report is
356
The bug assignee uses this field to prioritise his or her bugs.
357
It's a good idea not to change this on other people's bugs.</P
364
This indicates how severe the problem is - from blocker
365
("application unusable") to trivial ("minor cosmetic issue"). You
366
can also use this field to indicate whether a bug is an enhancement
374
(a.k.a. Target Milestone) A future version by which the bug is to
375
be fixed. e.g. The Bugzilla Project's milestones for future
376
Bugzilla versions are 2.18, 2.20, 3.0, etc. Milestones are not
377
restricted to numbers, thought - you can use any text strings, such
385
The person who filed the bug.</P
392
A list of people who get mail when the bug changes.</P
399
You can attach files (e.g. testcases or patches) to bugs. If there
400
are any attachments, they are listed in this section.</P
407
If this bug cannot be fixed unless other bugs are fixed (depends
408
on), or this bug stops other bugs being fixed (blocks), their
409
numbers are recorded here.</P
416
Whether this bug has any votes.</P
421
>Additional Comments:</EM
423
You can add your two cents to the bug discussion here, if you have
424
something worthwhile to say.</P
434
>3.1.3. Searching for Bugs</A
437
>The Bugzilla Search page is is the interface where you can find
438
any bug report, comment, or patch currently in the Bugzilla system. You
439
can play with it here:
441
HREF="http://landfill.bugzilla.org/bugzilla-2.16.7/query.cgi"
443
>http://landfill.bugzilla.org/bugzilla-2.16.7/query.cgi</A
448
>The Search page has controls for selecting different possible
449
values for all of the fields in a bug, as described above. Once you've
450
defined a search, you can either run it, or save it as a Remembered
451
Query, which can optionally appear in the footer of your pages.</P
453
>Highly advanced querying is done using Boolean Charts, which have
456
HREF="http://landfill.bugzilla.org/bugzilla-2.16.7/booleanchart.html"
458
> context-sensitive help</A
472
>If you run a search, a list of matching bugs will be returned.
473
The default search is to return all open bugs on the system - don't try
474
running this search on a Bugzilla installation with a lot of
477
>The format of the list is configurable. For example, it can be
478
sorted by clicking the column headings. Other useful features can be
479
accessed using the links at the bottom of the list:
491
this gives you a large page with a non-editable summary of the fields
500
change the bug attributes which appear in the list.</TD
505
>Change several bugs at once:</EM
508
If your account is sufficiently empowered, you can make the same
509
change to all the bugs in the list - for example, changing their
515
>Send mail to bug owners:</EM
518
Sends mail to the owners of all bugs on the list.</TD
523
>Edit this query:</EM
526
If you didn't get exactly the results you were looking for, you can
527
return to the Query page through this link and make small revisions
528
to the query you just made so you get more accurate results.</TD
543
>3.1.5. Filing Bugs</A
546
>Years of bug writing experience has been distilled for your
547
reading pleasure into the
549
HREF="http://landfill.bugzilla.org/bugzilla-2.16.7/bugwritinghelp.html"
551
> Bug Writing Guidelines</A
553
While some of the advice is Mozilla-specific, the basic principles of
554
reporting Reproducible, Specific bugs, isolating the Product you are
555
using, the Version of the Product, the Component which failed, the
556
Hardware Platform, and Operating System you were using at the time of
557
the failure go a long way toward ensuring accurate, responsible fixes
558
for the bug that bit you.</P
560
>The procedure for filing a test bug is as follows:</P
569
HREF="http://landfill.bugzilla.org/bugzilla-2.16.7/"
573
in your browser and click
575
HREF="http://landfill.bugzilla.org/bugzilla-2.16.7/enter_bug.cgi"
577
> Enter a new bug report</A
583
>Select a product - any one will do.</P
587
>Fill in the fields. Bugzilla should have made reasonable
588
guesses, based upon your browser, for the "Platform" and "OS"
589
drop-down boxes. If they are wrong, change them.</P
593
>Select "Commit" and send in your bug report.</P
603
SUMMARY="Footer navigation table"
632
HREF="hintsandtips.html"
b'\\ No newline at end of file'
added
removed
docs/html/how.html
