diff options
| author | gerv%gerv.net <> | 2004-01-25 03:30:57 +0100 |
|---|---|---|
| committer | gerv%gerv.net <> | 2004-01-25 03:30:57 +0100 |
| commit | 6c709dd097e65025038a0dc9c17fad6a88e99b6b (patch) | |
| tree | c0c33411898e67410829ea142458440fe912b388 /docs/html/programadmin.html | |
| parent | c7f3e4a3a055bbbec29a8731f388f9fa4648c768 (diff) | |
| download | bugzilla-6c709dd097e65025038a0dc9c17fad6a88e99b6b.tar.gz bugzilla-6c709dd097e65025038a0dc9c17fad6a88e99b6b.tar.xz | |
Massive rearrangement of the installation section. Hopefully it makes sense now.
Diffstat (limited to 'docs/html/programadmin.html')
| -rw-r--r-- | docs/html/programadmin.html | 395 |
1 files changed, 0 insertions, 395 deletions
diff --git a/docs/html/programadmin.html b/docs/html/programadmin.html deleted file mode 100644 index 119131417..000000000 --- a/docs/html/programadmin.html +++ /dev/null @@ -1,395 +0,0 @@ -<HTML -><HEAD -><TITLE ->Product, Component, Milestone, and Version Administration</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="Administering Bugzilla" -HREF="administration.html"><LINK -REL="PREVIOUS" -TITLE="User Administration" -HREF="useradmin.html"><LINK -REL="NEXT" -TITLE="Voting" -HREF="voting.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="useradmin.html" -ACCESSKEY="P" ->Prev</A -></TD -><TD -WIDTH="80%" -ALIGN="center" -VALIGN="bottom" ->Chapter 5. Administering Bugzilla</TD -><TD -WIDTH="10%" -ALIGN="right" -VALIGN="bottom" -><A -HREF="voting.html" -ACCESSKEY="N" ->Next</A -></TD -></TR -></TABLE -><HR -ALIGN="LEFT" -WIDTH="100%"></DIV -><DIV -CLASS="section" -><H1 -CLASS="section" -><A -NAME="programadmin" -></A ->5.3. Product, Component, Milestone, and Version Administration</H1 -><DIV -CLASS="section" -><H2 -CLASS="section" -><A -NAME="products" -></A ->5.3.1. Products</H2 -><P -> <A -HREF="glossary.html#gloss-product" -><I -CLASS="glossterm" -> Products</I -></A -> - - are the broadest category in Bugzilla, and tend to represent real-world - shipping products. E.g. if your company makes computer games, - you should have one product per game, perhaps a "Common" product for - units of technology used in multiple games, and maybe a few special - products (Website, Administration...)</P -><P ->Many of Bugzilla's settings are configurable on a per-product - basis. The number of "votes" available to users is set per-product, - as is the number of votes - required to move a bug automatically from the UNCONFIRMED status to the - NEW status.</P -><P ->To create a new product:</P -><P -></P -><OL -TYPE="1" -><LI -><P ->Select "products" from the footer</P -></LI -><LI -><P ->Select the "Add" link in the bottom right</P -></LI -><LI -><P ->Enter the name of the product and a description. The - Description field may contain HTML.</P -></LI -></OL -><P ->Don't worry about the "Closed for bug entry", "Maximum Votes - per person", "Maximum votes a person can put on a single bug", - "Number of votes a bug in this Product needs to automatically get out - of the UNCOMFIRMED state", and "Version" options yet. We'll cover - those in a few moments. - </P -></DIV -><DIV -CLASS="section" -><H2 -CLASS="section" -><A -NAME="components" -></A ->5.3.2. Components</H2 -><P ->Components are subsections of a Product. E.g. the computer game - you are designing may have a "UI" - component, an "API" component, a "Sound System" component, and a - "Plugins" component, each overseen by a different programmer. It - often makes sense to divide Components in Bugzilla according to the - natural divisions of responsibility within your Product or - company.</P -><P -> Each component has a owner and (if you turned it on in the parameters), - a QA Contact. The owner should be the primary person who fixes bugs in - that component. The QA Contact should be the person who will ensure - these bugs are completely fixed. The Owner, QA Contact, and Reporter - will get email when new bugs are created in this Component and when - these bugs change. Default Owner and Default QA Contact fields only - dictate the - <EM ->default assignments</EM ->; - these can be changed on bug submission, or at any later point in - a bug's life.</P -><P ->To create a new Component:</P -><P -></P -><OL -TYPE="1" -><LI -><P ->Select the "Edit components" link from the "Edit product" - page</P -></LI -><LI -><P ->Select the "Add" link in the bottom right.</P -></LI -><LI -><P ->Fill out the "Component" field, a short "Description", - the "Initial Owner" and "Initial QA Contact" (if enabled.) - The Component and Description fields may contain HTML; - the "Initial Owner" field must be a login name - already existing in the database. - </P -></LI -></OL -></DIV -><DIV -CLASS="section" -><H2 -CLASS="section" -><A -NAME="versions" -></A ->5.3.3. Versions</H2 -><P ->Versions are the revisions of the product, such as "Flinders - 3.1", "Flinders 95", and "Flinders 2000". Version is not a multi-select - field; the usual practice is to select the most recent version with - the bug. - </P -><P ->To create and edit Versions:</P -><P -></P -><OL -TYPE="1" -><LI -><P ->From the "Edit product" screen, select "Edit Versions"</P -></LI -><LI -><P ->You will notice that the product already has the default - version "undefined". Click the "Add" link in the bottom right.</P -></LI -><LI -><P ->Enter the name of the Version. This field takes text only. - Then click the "Add" button.</P -></LI -></OL -></DIV -><DIV -CLASS="section" -><H2 -CLASS="section" -><A -NAME="milestones" -></A ->5.3.4. Milestones</H2 -><P ->Milestones are "targets" that you plan to get a bug fixed by. For - example, you have a bug that you plan to fix for your 3.0 release, it - would be assigned the milestone of 3.0.</P -><DIV -CLASS="note" -><P -></P -><TABLE -CLASS="note" -WIDTH="100%" -BORDER="0" -><TR -><TD -WIDTH="25" -ALIGN="CENTER" -VALIGN="TOP" -><IMG -SRC="../images/note.gif" -HSPACE="5" -ALT="Note"></TD -><TD -ALIGN="LEFT" -VALIGN="TOP" -><P ->Milestone options will only appear for a Product if you turned - on the "usetargetmilestone" Param in the "Edit Parameters" screen. - </P -></TD -></TR -></TABLE -></DIV -><P ->To create new Milestones, set Default Milestones, and set - Milestone URL:</P -><P -></P -><OL -TYPE="1" -><LI -><P ->Select "Edit milestones" from the "Edit product" page.</P -></LI -><LI -><P ->Select "Add" in the bottom right corner. - text</P -></LI -><LI -><P ->Enter the name of the Milestone in the "Milestone" field. You - can optionally set the "sortkey", which is a positive or negative - number (-255 to 255) that defines where in the list this particular - milestone appears. This is because milestones often do not - occur in alphanumeric order For example, "Future" might be - after "Release 1.2". Select "Add".</P -></LI -><LI -><P ->From the Edit product screen, you can enter the URL of a - page which gives information about your milestones and what - they mean. </P -><DIV -CLASS="tip" -><P -></P -><TABLE -CLASS="tip" -WIDTH="100%" -BORDER="0" -><TR -><TD -WIDTH="25" -ALIGN="CENTER" -VALIGN="TOP" -><IMG -SRC="../images/tip.gif" -HSPACE="5" -ALT="Tip"></TD -><TD -ALIGN="LEFT" -VALIGN="TOP" -><P ->If you want your milestone document to be restricted so - that it can only be viewed by people in a particular Bugzilla - group, the best way is to attach the document to a bug in that - group, and make the URL the URL of that attachment.</P -></TD -></TR -></TABLE -></DIV -></LI -></OL -></DIV -></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="useradmin.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="voting.html" -ACCESSKEY="N" ->Next</A -></TD -></TR -><TR -><TD -WIDTH="33%" -ALIGN="left" -VALIGN="top" ->User Administration</TD -><TD -WIDTH="34%" -ALIGN="center" -VALIGN="top" -><A -HREF="administration.html" -ACCESSKEY="U" ->Up</A -></TD -><TD -WIDTH="33%" -ALIGN="right" -VALIGN="top" ->Voting</TD -></TR -></TABLE -></DIV -></BODY -></HTML ->
\ No newline at end of file |