5.3.1. products

products 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...)

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.

to create a new product:

1. select "products" from the footer

2. select the "add" link in the bottom right

3. enter the name of the product and a description. the description field may contain html.

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.

5.3.2. components

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.

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 default assignments; these can be changed on bug submission, or at any later point in a bug's life.

to create a new component:

1. select the "edit components" link from the "edit product" page

2. select the "add" link in the bottom right.

3. 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.

5.3.3. versions

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.

to create and edit versions:

1. from the "edit product" screen, select "edit versions"

2. you will notice that the product already has the default version "undefined". click the "add" link in the bottom right.

3. enter the name of the version. this field takes text only. then click the "add" button.

5.3.4. milestones

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.

milestone options will only appear for a product if you turned on the "usetargetmilestone" param in the "edit parameters" screen.

to create new milestones, set default milestones, and set milestone url:

1. select "edit milestones" from the "edit product" page.

2. select "add" in the bottom right corner. text

3. 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".

4. from the edit product screen, you can enter the url of a page which gives information about your milestones and what they mean.

   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.