1
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
5
>Anatomy of a Bug</TITLE
8
CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK
10
TITLE="The Bugzilla Guide - 3.0.4 Release"
11
HREF="index.html"><LINK
13
TITLE="Using Bugzilla"
14
HREF="using.html"><LINK
16
TITLE="Create a Bugzilla Account"
17
HREF="myaccount.html"><LINK
19
TITLE="Life Cycle of a Bug"
20
HREF="lifecycle.html"></HEAD
31
SUMMARY="Header navigation table"
40
>The Bugzilla Guide - 3.0.4 Release</TH
56
>Chapter 5. Using Bugzilla</TD
77
>5.3. Anatomy of a Bug</A
80
>The core of Bugzilla is the screen which displays a particular
81
bug. It's a good place to explain some Bugzilla concepts.
83
HREF="http://landfill.bugzilla.org/bugzilla-3.0-branch/show_bug.cgi?id=1"
85
> Bug 1 on Landfill</A
88
is a good example. Note that the labels for most fields are hyperlinks;
89
clicking them will take you to context-sensitive help on that
90
particular field. Fields marked * may not be present on every
91
installation of Bugzilla.</P
99
>Product and Component</EM
101
Bugs are divided up by Product and Component, with a Product
102
having one or more Components in it. For example,
103
bugzilla.mozilla.org's "Bugzilla" Product is composed of several
115
Administration of a Bugzilla installation.</TD
120
>Bugzilla-General:</EM
122
Anything that doesn't fit in the other components, or spans
123
multiple components.</TD
128
>Creating/Changing Bugs:</EM
130
Creating, changing, and viewing bugs.</TD
137
The Bugzilla documentation, including The Bugzilla Guide.</TD
144
Anything to do with email sent by Bugzilla.</TD
151
The installation process of Bugzilla.</TD
158
Anything to do with searching for bugs and viewing the
164
>Reporting/Charting:</EM
166
Getting reports from Bugzilla.</TD
173
Anything about managing a user account from the user's perspective.
174
Saved queries, creating accounts, changing passwords, logging in,
182
General issues having to do with the user interface cosmetics (not
183
functionality) including cosmetic issues, HTML templates,
196
>Status and Resolution:</EM
199
These define exactly what state the bug is in - from not even
200
being confirmed as a bug, through to being fixed and the fix
201
confirmed by Quality Assurance. The different possible values for
202
Status and Resolution on your installation should be documented in the
203
context-sensitive help for those items.</P
210
The person responsible for fixing the bug.</P
217
The person responsible for quality assurance on this bug.</P
224
A URL associated with the bug, if any.</P
231
A one-sentence summary of the problem.</P
236
>*Status Whiteboard:</EM
238
(a.k.a. Whiteboard) A free-form text area for adding short notes
239
and tags to a bug.</P
246
The administrator can define keywords which you can use to tag and
247
categorise bugs - e.g. The Mozilla Project has keywords like crash
253
>Platform and OS:</EM
255
These indicate the computing environment where the bug was
263
The "Version" field is usually used for versions of a product which
264
have been released, and is set to indicate which versions of a
265
Component have the particular problem the bug report is
273
The bug assignee uses this field to prioritize his or her bugs.
274
It's a good idea not to change this on other people's bugs.</P
281
This indicates how severe the problem is - from blocker
282
("application unusable") to trivial ("minor cosmetic issue"). You
283
can also use this field to indicate whether a bug is an enhancement
291
(a.k.a. Target Milestone) A future version by which the bug is to
292
be fixed. e.g. The Bugzilla Project's milestones for future
293
Bugzilla versions are 2.18, 2.20, 3.0, etc. Milestones are not
294
restricted to numbers, thought - you can use any text strings, such
302
The person who filed the bug.</P
309
A list of people who get mail when the bug changes.</P
316
This form can be used for time tracking.
317
To use this feature, you have to be blessed group membership
318
specified by the <SPAN
320
>"timetrackinggroup"</SPAN
332
This field shows the original estimated time.</TD
339
This field shows the current estimated time.
340
This number is calculated from <SPAN
342
>"Hours Worked"</SPAN
354
This field shows the number of hours worked.</TD
361
This field shows the <SPAN
363
>"Current Est."</SPAN
367
>"Hours Worked"</SPAN
371
>"Hours Worked"</SPAN
380
This field shows what percentage of the task is complete.</TD
387
This field shows the number of hours that the bug is ahead of the
398
This field shows the deadline for this bug.</TD
412
You can attach files (e.g. testcases or patches) to bugs. If there
413
are any attachments, they are listed in this section. Attachments are
414
normally stored in the Bugzilla database, unless they are marked as
415
Big Files, which are stored directly on disk.
423
If this bug cannot be fixed unless other bugs are fixed (depends
424
on), or this bug stops other bugs being fixed (blocks), their
425
numbers are recorded here.</P
432
Whether this bug has any votes.</P
437
>Additional Comments:</EM
439
You can add your two cents to the bug discussion here, if you have
440
something worthwhile to say.</P
449
SUMMARY="Footer navigation table"
460
HREF="myaccount.html"
478
HREF="lifecycle.html"
488
>Create a Bugzilla Account</TD
502
>Life Cycle of a Bug</TD
b'\\ No newline at end of file'