Quick Bugzilla Tutorial

Bugzilla is a “Bug Tracking System” that can efficiently keep track of outstanding bugs in a product. Multiple users can access this database and query, add and manage these bugs. Bugzilla essentially comes to the rescue of a group of people working together on a product as it enables them to view current bugs and make contributions to resolve issues.


Its basic repository nature works out better than the mailing list concept and an organized database is always easier to work with.


The bugzilla utility basically allows you to do the following:

  • Add a bug into the database

  • Review existing bug reports

  • Manage the content


Bugzilla is organised in the form of bug reports that give all the information you need about a particular bug. A bug report would consist of the following fields.


  • Product–>Component

  • Assigned to

  • Status (New, Assigned, Fixed etc)

  • Summary

  • Bug priority

  • Bug severity (blocker, trivial etc)

  • Bug reporter


A Bug’s Life:


Once a new bug is entered, it goes through a number of states before the issue is resolved. A bug’s life as we term it has the following states an transitions:


  1. unconfirmed

  2. new (this state is acquired once the bug is confirmed)

  3. assigned (once a developer takes possession of the bug)

  4. resolved (when the development with the bug is finished)

  5. reopen (when the solution is not satisfactory)

  6. verified (once the solution is verified and satisfactory)

  7. closed

For a better understanding view: http://www.bugzilla.org/docs/2.18/images/bzLifecycle.png


Bugzilla Query Page:


The Bugzilla search page allows you to search for a particular bug. The search can be based on the product, status or description. To refine your search an advanced search option is available.


The result page lists the bugs based on relevance to the search.


Adding a new bug:


In order to add a new bug, or even query, you need to have an account which you log into.


  • Click on “Enter New Bug”. This takes you to a page containing the list of products.

  • Select the relevant product.

  • Now you can make your report more specific by selecting the component, target etc. At this point you are the “reporter” of that bug and the status of that bug is set to NEW.

  • You can assign the bug to a particular person and provide his email id in the “Assign to” field. Appropriately you can add people in CC also. Alternatively, you can use it as a reporting mechanism where you don’t assign the bug to anyone but just add the right people who could solve your problem in the CC list. Anybody who wishes to take it up can re-assign it to himself later.

  • Give a one-line summary and a short description of the bug.

  • It is a good practice to use the keywords listed.

  • Once finished, click on “commit” to file your report.


Managing your bug report:


  • If you want to resolve a bug that is assigned to, you need to first accept the bug and change its state to ASSIGNED. Then you can resolve it.

  • Commenting option is also available where you can make suggestions, if any.

  • If you want to resolve bugs not assigned to you, re-assign it to yourself and do so.


For a complete Bugzilla tutorial use this link:




This entry was posted in trivia, tutorials. Bookmark the permalink.

5 Responses to Quick Bugzilla Tutorial

  1. tesmond says:

    Surprise missing features:

    1. The ability to edit the description after submitting a bug. Requires direct SQL access to achieve this if you need to. (alternatives of deletion and re-submitting increase work load, and adding comments again is an unnecessary increase in work load.

    2. Re-assign user drop down list. Bugzilla fails to provide a list of users and instead requires the typing in of the full email address.

    3. No quick method of viewing the full display of single records from a list of records, you need to narrow down the list to 1 bug first.

  2. S.M.Umair.M says:

    This may be a bug repository, but you cant name it Bug Tracking Software, as it hasnot any automation function of testing, it has just repository function.

  3. S.M.Umair.M says:

    Try to Use “VERSIONONE” its very nice, easy to use and friendly enviroment as well as easiest and accessible way of Bug reporting and follow-up procedure.


  4. fred says:


    This page is in error 404:

    Thanks for the tutorial, maybe you can mention somewhere that bugzilla is free 😀

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s