Bugzilla: A Brief Tutorial

Bugzilla: A Brief Tutorial Index What is Bugzilla?.............................................................................................................3 How do I gain access?......................................................................................................3 How do I change my account settings?............................................................................3 How are bugs organized?.................................................................................................4 How do I submit a bug? ...................................................................................................5 What are bugs made of?...................................................................................................5 How do I search for a bug? ..............................................................................................7 What is the lifecycle of a bug?.........................................................................................8

Bugzilla page 3 of 8 The complete documentation for Bugzilla can be found at www.Bugzilla.org/docs/2.18/html/

What is Bugzilla?
Bugzilla is the world-leading free software bug tracking system. You can access University of South Dakotas Bugzilla by going to http://biota.usd.edu/

How do I gain access?

In order to use Bugzilla you need to create an account. To create an account you first click the "Open a new Bugzilla account" link on the main page. Then, enter your email address and, optionally, your name in the spaces provided, then click "Create Account." Next you should receive an email to the address you provided, which contains your login name (generally the same as the email address), and a password. This password is randomly generated, but can be changed to something more memorable. Finally click the "Log In" link in the footer at the bottom of the page in your browser, enter your email address and password into the spaces provided, and click "Login."

How do I change my account settings?

Once you have logged in, you can customize various aspects of Bugzilla through the "Edit prefs" link in the page footer. The preferences are split into three tabs Account settings: On this tab, you can change your basic account information, including your password, email address and real name. For security reasons, in order to change anything on this page you must type your current password into the "Password" field at the top of the page. If you attempt to change your email address, a confirmation email is sent to both the old and new addresses, with a link to use to confirm the change. Email settings: This tab controls the amount of email Bugzilla sends you. In general, users have almost complete control over how much (or how little) email Bugzilla sends them. If you want to

7/27/2005

Bugzilla page 4 of 8 receive the maximum amount of email possible, click the "Enable All Mail" button. If you don't want to receive any email from Bugzilla at all, click the "Disable All Mail" button To fine-tune your bug mail, decide the events for which you want to receive bug mail; then decide if you want to receive it all the time (enable the checkbox for every column), or only when you have a certain relationship with a bug (enable the checkbox only for those columns).. Saved searches: Bugzilla allows you to save searches and have them displayed in the footer of every page. On the saved searches tab you can control which searches are displayed to you, simply by un-checking the box. Permissions: This is a purely informative page which outlines your current permissions on this installation of Bugzilla - what product groups you are in, and whether you can edit bugs or perform various administration functions.

How are bugs organized?

The broadest category of bugs is products. Normally products represent a single piece of software or entity. The category directly below products is components. A component is a subsection of a Product. It should be a narrow category, tailored to your organization. All Products must contain at least one Component (and, as a matter of fact, creating a Product with no Components will create an error in Bugzilla). Then finally there is a bug. A "bug" in Bugzilla refers to an issue entered into the database which has an associated number, assignments, comments, etc. Some also refer to a "tickets" or "issues"; in the context of Bugzilla, they are synonymous. An example of Bugzillas organization of its bugs would be a video game development company. With each product being a different game, Packman and Ms. Packman would be different products. A component for each one of those games would be the sound or graphics.

7/27/2005

Bugzilla page 5 of 8 Then finally you have the bug. This would be that Ms. Packman is able to go through walls on level two.

How do I submit a bug?

Before you enter your bug, search for the bug to determine whether the defect you've discovered is a known, already-reported bug. If your bug is the 37th duplicate of a known issue, you're more likely to annoy the person in charge of that area. Next, be sure to reproduce your bug using a recent build. Engineers tend to be most interested in problems affecting the code base that they're actively working on. After all, the bug you're reporting may already be fixed. If you've discovered a new bug using a current build, report it in Bugzilla. From your Bugzilla main page at http://biota.usd.edu/, choose "Enter a new bug". Select the product that you've found a bug in, and enter your e-mail address, password, and press the "Login" button. Fill in the fields. Bugzilla should have made reasonable guesses, based upon your browser, for the "Platform" and "OS" drop-down boxes. If they are wrong, change them. Select "Commit" and send in your bug report.

What are bugs made of?

There are several parts to a bug here is a list, and a short description of them. Status and Resolution: 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. Assigned To: The person responsible for fixing the bug. URL: A URL associated with the bug, if any. Summary: A one-sentence summary of the problem.

7/27/2005

Bugzilla page 6 of 8 Status Whiteboard: (a.k.a. Whiteboard) A free-form text area for adding short notes and tags to a bug. Keywords: The administrator can define keywords which you can use to tag and categorize bugs - e.g. The Mozilla Project has keywords like crash and regression. Platform and OS: These indicate the computing environment where the bug was found. Version: 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. Priority: The bug assignee uses this field to priorities his or her bugs. It's a good idea not to change this on other people's bugs. Severity: 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. Target: (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. Reporter: The person who filed the bug. CC list: A list of people who get mail when the bug changes. Attachments: You can attach files (e.g. test cases or patches) to bugs. If there are any attachments, they are listed in this section. Dependencies: 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. Votes: Whether this bug has any votes.

7/27/2005

Bugzilla page 7 of 8 Additional Comments: You can add your two cents to the bug discussion here, if you have something worthwhile to say

How do I search for a bug?

The Bugzilla Search page is the interface where you can find any bug report, comment, or patch currently in the Bugzilla system. The Search page has controls for selecting different possible values for all of the fields in a bug, as described above. For some fields, multiple values can be selected. In those cases, Bugzilla returns bugs where the content of the field matches any one of the selected values. If none is selected, then the field can take any value. Once you've run a search, you can save it as a Saved Search, which appears in the page footer. When you hit search, Bugzilla will return a page with the bugs that matches your search criteria. The format of the list is configurable. For example, it can be sorted by clicking the column headings. Other useful features can be accessed using the links at the bottom of the list: Long Format: this gives you a large page with a non-editable summary of the fields of each bug. CSV: get the bug list as comma-separated values, for import into e.g. a spreadsheet. Change Columns: change the bug attributes which appear in the list. Change several bugs at once: If your account is sufficiently empowered, you can make the same change to all the bugs in the list - for example, changing their owner. Send mail to bug owners: Sends mail to the owners of all bugs on the list. Edit Search: If you didn't get exactly the results you were looking for, you can return to the Query page through this link and make small revisions to the query you just made so you get more accurate results. Remember Search As: You can give a search a name and remember it; a link will appear in your page footer giving you quick access to run it again later

7/27/2005

Bugzilla page 8 of 8

What is the lifecycle of a bug?

Like everything in life a bug must be born and die. These are the steps that it goes through. As you can see there are several different tacks a bug can take before it becomes closed or resolved.

7/27/2005