Bugs

The Bug Enquiry screen shows all the Bugs assigned to your project. There is no limit to the number of Bugs which may be assigned to a Project.

A Bug is defined as any problem in existing functionality, or functionality that is missing. A bug is assigned to a specific Requirement.

Click the Add button to add a new Bug

Click the User name to edit an existing Bug

Either way, the Bug Maintenance screen will be displayed, below.

:) The tabs provide a filter so that the screen only shows bugs of a selected Status. The screen above shows 'All Bugs' for the Project.

:) The ^ symbol indicates that the list can be sorted on this column.

Bug Maintenance.

This screen is where you add Bug records or change existing Bugs.

You should determine your own process for managing bugs using this system. We recommend:-

• Tester raises the bug, including the Steps to reproduce the bug. The tester should assign the Bug to the appropriate Requirement. When ready the Tester assigns the bug to a Developer.
• Developer reproduces the bug, corrects it, makes notes in the Fix Log (dating entries may be required) and assigns the Bug to the Tester.
• Tester retests the bug. If fixed, the Tester closes the bug. If not fixed, the Tester makes additional notes and assigns to Developer.
• Only the Tester can close the Bug.

Fields Shown:-