1
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
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="Administering Bugzilla"
14
HREF="administration.html"><LINK
17
HREF="products.html"><LINK
20
HREF="versions.html"></HEAD
31
SUMMARY="Header navigation table"
40
>The Bugzilla Guide - 3.0.4 Release</TH
56
>Chapter 3. Administering Bugzilla</TD
80
>Components are subsections of a Product. E.g. the computer game
81
you are designing may have a "UI"
82
component, an "API" component, a "Sound System" component, and a
83
"Plugins" component, each overseen by a different programmer. It
84
often makes sense to divide Components in Bugzilla according to the
85
natural divisions of responsibility within your Product or
88
> Each component has a default assignee and (if you turned it on in the parameters),
89
a QA Contact. The default assignee should be the primary person who fixes bugs in
90
that component. The QA Contact should be the person who will ensure
91
these bugs are completely fixed. The Assignee, QA Contact, and Reporter
92
will get email when new bugs are created in this Component and when
93
these bugs change. Default Assignee and Default QA Contact fields only
96
>default assignments</EM
98
these can be changed on bug submission, or at any later point in
101
>To create a new Component:</P
110
>"Edit components"</SPAN
114
>"Edit product"</SPAN
122
> link in the bottom right.</P
136
>"Default Assignee"</SPAN
139
>"Default CC List"</SPAN
143
>"Default QA Contact"</SPAN
147
>"Component Description"</SPAN
148
> field may contain a
149
limited subset of HTML tags. The <SPAN
151
>"Default Assignee"</SPAN
153
field must be a login name already existing in the Bugzilla database.
163
SUMMARY="Footer navigation table"
208
HREF="administration.html"
b'\\ No newline at end of file'