Archive for the ‘Bug Tracking Tool’ Category

English: based on the graphics by FoeNyx

Bugzilla:                                                                                                                                                                                            

Bugzilla is a defect tracking tool originally developed and used by the Mozilla project, and licensed under the Mozilla Public License.

Features:

  • Optimized database structure for increased performance and scalability
  • Excellent security to protect confidentiality
  • Advanced query tool that can remember your searches
  • Integrated email capabilities
  • Editable user profiles and comprehensive email preferences
  • Comprehensive permissions system

Benefits

  • Improve communication
  • Increase product quality
  • Improve customer satisfaction
  • Ensure accountability
  • Increase productivity
  • Bugzilla can adapt to multiple situations

You can download bugzilla from http://www.bugzilla.org/download/ link.

Home screen of bugzilla appears as:

Steps to create account:

If you want to use Bugzilla, first you need to create an account. Consult with the administrator responsible for your installation of Bugzilla for the URL you should use to access it.

  1. Click the “Open a new Bugzilla account” link, enter your email address and, optionally, your name in the spaces provided, then click “Create Account” .
  2. Within moments, you should receive an email to the address you provided above, which contains your login name (generally the same as the email address), and a password you can use to access your account. This password is randomly generated, and can be changed to something more memorable.
  3. Click the “Log In” link in the yellow area at the bottom of the page in your browser, enter your email address and password into the spaces provided, and click “Login”.

Fields/components of a bug in bugzilla:

Product and component: Bugs are divided up by Product and Component, with a Product having one or more Components in it.

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.

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 categorise 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 prioritise 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. testcases 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.

 Additional Comments: You can add your two cents to the bug discussion here, if you have something worthwhile to say.

Steps to fire a bug:

Click on fire a bug icon on home screen of bugzilla.

Pick a product on which you want to fire/enter a bug.

Then fill all the fields like component, version, severity, hardware, os, summary, description etc.

Add attachment/screenshot if you have.

Click on submit button.

Note: Bug id is generated after clicking on submit button, please note it for further communication or reference.

Advertisements