The document provides an overview of Bugzilla, an open source bug tracking tool. It describes Bugzilla's origins and lifecycle. It also summarizes Bugzilla's user permissions system, email notification preferences, definitions of terms like products and components, how bugs flow through the system, searching for bugs, and the bug lifecycle. The document uses examples to illustrate classifications, submitting a new bug, and generating summary reports in tabular and graphical formats.

1. Bugzilla Prepared By : Charul Bhan

2. Introduction Web-based general purpose bugtracker tool Released as open source software by Netscape Communications in 1998 Originally written in Tcl, later ported to Perl before its release as part of Netscape's early open source code Bugzilla Lifecycle

3. Main Page

4. Create user For creation of new account, first user has to submit his email address to administrator. Administrator provides him the link to create a password with email address as a user name.

5. User Permissions

6. User Permissions Contd…

7. Add User From the main page, select the users link provided at the bottom of the page.

8. Add User Contd…

9. Add User Contd…

10. Email Preferences Prepared By : Charul Bhan

11. Email Preferences User can use email notification to keep himself informed about the various changes taking place in the bug. These preferences are user configurable so that any user can customized it to his own needs.

12. Email Preferences Contd…

13. Email Preferences Contd…

14. Bugzilla Intricacies Prepared By : Charul Bhan

15. Definitions Product A Product is a broad category of types of bugs, normally representing a single piece of software or entity. They can be considered as the project under one domain. Components A Component is a subsection of a Product. It should be a narrow category, tailored to an organization. All Products must contain at least one Component . These components can be correlated with the various sub divisions within the project. Classification Broadly speaking , they are collection of one or more products. These can be loosely termed as a domain.

16. Classification

17. Classification Contd…

18. Product flow 1

19. Product Flow 1 Contd…

20. Product Flow 2

21. Product Flow 2 Contd…

22. Component Flow 1

23. Component Flow 1 Contd...

24. Component Flow 2

25. Component Flow 2 Contd…

26. Component Flow 2 Contd…

27. Bug Searching Prepared By : Charul Bhan

28. Search Bug

29. Search Bug Contd…

30. Search Bug Contd…

31. Search Bug Contd…

32. Bug Life Cycle Prepared By : Charul Bhan

33. Example Classification : Gaming The Domain here considered is the ever-growing Gaming industry Products: Mobile Gaming, PC Gaming Above mentioned are two products of the gaming industry. Here we will look at the bug pertaining to the Mobile gaming. Components: Functional , language, UI (user interface) The bug will correspond to the UI component of Mobile Gaming

34. New Bug Main Page

35. New Bug Contd… QA Contact: User responsible for quality assurance of this bug Deadline: This field shows the deadline for this bug. Estimated Hours: This field shows the original estimated time.

36. New Bug Contd… Depends on: This field gives dependency of this bug on the bug specified. Blocks: This field specifies the bug which is prevented from being fixed until this bug is fixed Selecting the Commit button results into submission of bug and simultaneously an mail is send to the QA contacts of the bug.

37. Assigned state

38. Assigned state Contd…

39. Bug fixing

40. Bug verification

41. Summary Reports Prepared By : Charul Bhan

42. Summary Reports Provide information pertaining to the bugs present in the software in documented form. The information can either be observed in tabular form or pictorial form.

43. Summary Reports Contd…

44. Tabular Report Summary Reports Contd…

45. Tabular Report Summary Reports Contd… Vertical axis: Component Horizontal axis: Priority

46. Summary Reports Contd… Graphical Report

47. Summary Reports Contd…

48. Thanks