This document provides an overview of change management and bug tracking using Bugzilla as an example tool. It explains what a bug and bug report are, describes the Bugzilla bug tracking system and its open source nature. It then outlines the basic bug lifecycle process in Bugzilla of finding, reporting, assigning, resolving, verifying, reopening and closing bugs.
15. Actioningnew bugs Bug gets assigned to someone They get emailed They decide what should be done Will set it as Assigned, and set the Target Milestone Priority 15
16. Assigned Active / In-progress More information might be required Gets fixed “Resolved” Comments added stating the Changes made 16
19. Reopened Reassigned back to the engineer that stated it was Fixed The Fixed-Reopened loop can continue 19
20. Closed Final state of the bug lifecycle A record of what was raised and fixed for reporting and historical searches 20
21. Conclusion I have covered :- What a bug and bug report is What Bugzilla is, and A basic overview of how it works A bug Lifecycle, and how it relates to Bugzilla Any questions? 21