Hey guys, in this post will learn about how to create a bug in Bugzilla.

Pre-requisite: If you don’t have a Bugzilla account create one here Create Bugzilla account.

Log in to the account with your credentials.

Step 1: Click New in the Bugzilla Main-page

Step 2: In the next window, first select the pre-defined product classification and next select the product of your choice from the product list. 

Screen Shot 2016-05-22 at 10.23.14 AM

Step 3: In the next screen,

  1. Select component
  2. Enter component description
  3. Select product version
  4. Select severity of the bug
  5. Select hardware
  6. Select OS
  7. Enter Summary
  8. Enter Description
  9. Add an attachment

Note : Required fields are marked with *. While submitting the bug should not leave those fields blank.


While you enter a summary of the bug, it will also show you the possible duplicates based on the keyword you enter.

possible duplicates

Add an Attachment to the bug by clicking the add an attachment button.


Choose file and Enter description for the attachment in the space given.


Step 4: Click Submit bug

Step 5 : #33781 bug is created successfully. Users will also have other options to add additional information about the bug like Milestones, Tags, URL, Deadline, CC List, Bug history,etc.

If your not sure what should be entered in the field, just click the label of the field that will navigate to the page where it describes the fields of the bug.


If you scroll down a bit, you will have additional options to change the status of the bug, add additional comments and finally save the changes.


You have successfully created a bug in bugzilla:)

In my next post, will learn about how to use the browse option to locate the bugs belongs to a specific product and component.

Have you tried Bugzilla?  Share your experience in the comments below.

Know anyone who would like to learn Bugzilla for enhancing their skills?  Let them know by sharing this article on Facebook, Twitter, or Google Plus.

Leave a Reply

Your email address will not be published. Required fields are marked *

Discover more from Letzdotesting

Subscribe now to keep reading and get access to the full archive.

Continue reading