[Craig Brass]

 bug_report.gif (9.06K)
Number of downloads: 1

Below is the process we go through when a new bug gets reported.

1. After a new bug has been submitted, one of the software architects checks to see if another bug report for this bug has been submitted. If it has, the bug is moved to the Duplicates board. If it hasn't then the architect continues.

They then check over the software to see if they can replicate the bug. If they can they then decide if this is how it should be working or if it is infact a bug. If it is how the software should be working, it is moved to the Not a Bug board but if it is it is moved to the Pending Being Fixed board.

If the architect is unable to replicate the bug, they post a reply requesting more information from the user. If the bug has been open for a while after this with no reply, the architect may choose to move it to the Not a Bug board anyway.

 down_arrow.gif (997bytes)
Number of downloads: 1

2. The software developers check over the Pending Being Fixed board daily. If they see a bug in there, they fix the bug as soon as possible. Once they fix the bug, they move it to the Fix Attempted board.

 down_arrow.gif (997bytes)
Number of downloads: 1

3. The architect that initially confirmed the bug will check the latest build of the software to confirm that it has actually been fixed. If it has, they will move it to the Fixed board. If it hasn't, it is placed back in the Pending Being Fixed board for further investigation by the developer that attempted to fix it.