summaryrefslogtreecommitdiffstats
path: root/docs/html/bug_page.html
diff options
context:
space:
mode:
authorgerv%gerv.net <>2004-01-16 07:34:12 +0100
committergerv%gerv.net <>2004-01-16 07:34:12 +0100
commit4bbb07e8048ef859cfc29c6b9d221840f2c6aed1 (patch)
tree69ebbdef36708c17345d3220223190a3ce0b682e /docs/html/bug_page.html
parent85e651ef9836d43613c3bb55f7c1c3ff150f76d0 (diff)
downloadbugzilla-4bbb07e8048ef859cfc29c6b9d221840f2c6aed1.tar.gz
bugzilla-4bbb07e8048ef859cfc29c6b9d221840f2c6aed1.tar.xz
Phase 1 of a big documentation update before 2.17.6.
Diffstat (limited to 'docs/html/bug_page.html')
-rw-r--r--docs/html/bug_page.html404
1 files changed, 404 insertions, 0 deletions
diff --git a/docs/html/bug_page.html b/docs/html/bug_page.html
new file mode 100644
index 000000000..ece7524cd
--- /dev/null
+++ b/docs/html/bug_page.html
@@ -0,0 +1,404 @@
+<HTML
+><HEAD
+><TITLE
+>Anatomy of a Bug</TITLE
+><META
+NAME="GENERATOR"
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
+REL="HOME"
+TITLE="The Bugzilla Guide - 2.17.5
+ Development Release"
+HREF="index.html"><LINK
+REL="UP"
+TITLE="Using Bugzilla"
+HREF="using.html"><LINK
+REL="PREVIOUS"
+TITLE="Create a Bugzilla Account"
+HREF="myaccount.html"><LINK
+REL="NEXT"
+TITLE="Searching for Bugs"
+HREF="query.html"></HEAD
+><BODY
+CLASS="section"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><DIV
+CLASS="NAVHEADER"
+><TABLE
+SUMMARY="Header navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TH
+COLSPAN="3"
+ALIGN="center"
+>The Bugzilla Guide - 2.17.5
+ Development Release</TH
+></TR
+><TR
+><TD
+WIDTH="10%"
+ALIGN="left"
+VALIGN="bottom"
+><A
+HREF="myaccount.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="80%"
+ALIGN="center"
+VALIGN="bottom"
+>Chapter 3. Using Bugzilla</TD
+><TD
+WIDTH="10%"
+ALIGN="right"
+VALIGN="bottom"
+><A
+HREF="query.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+></TABLE
+><HR
+ALIGN="LEFT"
+WIDTH="100%"></DIV
+><DIV
+CLASS="section"
+><H1
+CLASS="section"
+><A
+NAME="bug_page"
+></A
+>3.2. Anatomy of a Bug</H1
+><P
+>The core of Bugzilla is the screen which displays a particular
+ bug. It's a good place to explain some Bugzilla concepts.
+ <A
+HREF="http://landfill.bugzilla.org/bugzilla-tip/show_bug.cgi?id=1"
+TARGET="_top"
+>&#13; Bug 1 on Landfill</A
+>
+
+ is a good example. Note that the labels for most fields are hyperlinks;
+ clicking them will take you to context-sensitive help on that
+ particular field. Fields marked * may not be present on every
+ installation of Bugzilla.</P
+><P
+></P
+><OL
+TYPE="1"
+><LI
+><P
+>&#13; <EM
+>Product and Component</EM
+>:
+ Bugs are divided up by Product and Component, with a Product
+ having one or more Components in it. For example,
+ bugzilla.mozilla.org's "Bugzilla" Product is composed of several
+ Components:
+ <P
+></P
+><TABLE
+BORDER="0"
+><TBODY
+><TR
+><TD
+>&#13; <EM
+>Administration:</EM
+>
+ Administration of a Bugzilla installation.</TD
+></TR
+><TR
+><TD
+>&#13; <EM
+>Bugzilla-General:</EM
+>
+ Anything that doesn't fit in the other components, or spans
+ multiple components.</TD
+></TR
+><TR
+><TD
+>&#13; <EM
+>Creating/Changing Bugs:</EM
+>
+ Creating, changing, and viewing bugs.</TD
+></TR
+><TR
+><TD
+>&#13; <EM
+>Documentation:</EM
+>
+ The Bugzilla documentation, including The Bugzilla Guide.</TD
+></TR
+><TR
+><TD
+>&#13; <EM
+>Email:</EM
+>
+ Anything to do with email sent by Bugzilla.</TD
+></TR
+><TR
+><TD
+>&#13; <EM
+>Installation:</EM
+>
+ The installation process of Bugzilla.</TD
+></TR
+><TR
+><TD
+>&#13; <EM
+>Query/Buglist:</EM
+>
+ Anything to do with searching for bugs and viewing the
+ buglists.</TD
+></TR
+><TR
+><TD
+>&#13; <EM
+>Reporting/Charting:</EM
+>
+ Getting reports from Bugzilla.</TD
+></TR
+><TR
+><TD
+>&#13; <EM
+>User Accounts:</EM
+>
+ Anything about managing a user account from the user's perspective.
+ Saved queries, creating accounts, changing passwords, logging in,
+ etc.</TD
+></TR
+><TR
+><TD
+>&#13; <EM
+>User Interface:</EM
+>
+ General issues having to do with the user interface cosmetics (not
+ functionality) including cosmetic issues, HTML templates,
+ etc.</TD
+></TR
+></TBODY
+></TABLE
+><P
+></P
+>
+ </P
+></LI
+><LI
+><P
+>&#13; <EM
+>Status and Resolution:</EM
+>
+
+ These define exactly what state the bug is in - from not even
+ being confirmed as a bug, through to being fixed and the fix
+ confirmed by Quality Assurance. The different possible values for
+ Status and Resolution on your installation should be documented in the
+ context-sensitive help for those items.</P
+></LI
+><LI
+><P
+>&#13; <EM
+>Assigned To:</EM
+>
+ The person responsible for fixing the bug.</P
+></LI
+><LI
+><P
+>&#13; <EM
+>*URL:</EM
+>
+ A URL associated with the bug, if any.</P
+></LI
+><LI
+><P
+>&#13; <EM
+>Summary:</EM
+>
+ A one-sentence summary of the problem.</P
+></LI
+><LI
+><P
+>&#13; <EM
+>*Status Whiteboard:</EM
+>
+ (a.k.a. Whiteboard) A free-form text area for adding short notes
+ and tags to a bug.</P
+></LI
+><LI
+><P
+>&#13; <EM
+>*Keywords:</EM
+>
+ The administrator can define keywords which you can use to tag and
+ categorise bugs - e.g. The Mozilla Project has keywords like crash
+ and regression.</P
+></LI
+><LI
+><P
+>&#13; <EM
+>Platform and OS:</EM
+>
+ These indicate the computing environment where the bug was
+ found.</P
+></LI
+><LI
+><P
+>&#13; <EM
+>Version:</EM
+>
+ The "Version" field is usually used for versions of a product which
+ have been released, and is set to indicate which versions of a
+ Component have the particular problem the bug report is
+ about.</P
+></LI
+><LI
+><P
+>&#13; <EM
+>Priority:</EM
+>
+ The bug assignee uses this field to prioritise his or her bugs.
+ It's a good idea not to change this on other people's bugs.</P
+></LI
+><LI
+><P
+>&#13; <EM
+>Severity:</EM
+>
+ This indicates how severe the problem is - from blocker
+ ("application unusable") to trivial ("minor cosmetic issue"). You
+ can also use this field to indicate whether a bug is an enhancement
+ request.</P
+></LI
+><LI
+><P
+>&#13; <EM
+>*Target:</EM
+>
+ (a.k.a. Target Milestone) A future version by which the bug is to
+ be fixed. e.g. The Bugzilla Project's milestones for future
+ Bugzilla versions are 2.18, 2.20, 3.0, etc. Milestones are not
+ restricted to numbers, thought - you can use any text strings, such
+ as dates.</P
+></LI
+><LI
+><P
+>&#13; <EM
+>Reporter:</EM
+>
+ The person who filed the bug.</P
+></LI
+><LI
+><P
+>&#13; <EM
+>CC list:</EM
+>
+ A list of people who get mail when the bug changes.</P
+></LI
+><LI
+><P
+>&#13; <EM
+>Attachments:</EM
+>
+ You can attach files (e.g. testcases or patches) to bugs. If there
+ are any attachments, they are listed in this section.</P
+></LI
+><LI
+><P
+>&#13; <EM
+>*Dependencies:</EM
+>
+ If this bug cannot be fixed unless other bugs are fixed (depends
+ on), or this bug stops other bugs being fixed (blocks), their
+ numbers are recorded here.</P
+></LI
+><LI
+><P
+>&#13; <EM
+>*Votes:</EM
+>
+ Whether this bug has any votes.</P
+></LI
+><LI
+><P
+>&#13; <EM
+>Additional Comments:</EM
+>
+ You can add your two cents to the bug discussion here, if you have
+ something worthwhile to say.</P
+></LI
+></OL
+></DIV
+><DIV
+CLASS="NAVFOOTER"
+><HR
+ALIGN="LEFT"
+WIDTH="100%"><TABLE
+SUMMARY="Footer navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+><A
+HREF="myaccount.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="index.html"
+ACCESSKEY="H"
+>Home</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+><A
+HREF="query.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+>Create a Bugzilla Account</TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="using.html"
+ACCESSKEY="U"
+>Up</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+>Searching for Bugs</TD
+></TR
+></TABLE
+></DIV
+></BODY
+></HTML
+> \ No newline at end of file