I think

Develeoper tester test lead

When I see a defect in the application in the testing process I go to the Defects

Tab and click on Add Defect button and enter the details of the defect and attach

any snapshots of the defect and close it. The status New will be assigned to

that defect. I can mail that defect to the concerned developer from TestDirector

or ask the developer to take a look at the defect in TestDirector. Developer after

seeing the defect can change the status to Open which means he/she is

working on fixing it. When the fixing is done the developer can change the status

to Fixed . When developer feels it not required to fix at that moment he changes the status as DIFFERED. I can then retest the defect after the fresh build of the application and if found satisfied I can Close the defect or Reopen it if I am not satisfied or the defect is not fixed.

The developer has the right to Reject the defect with proper reason attached to

it if he/she thinks that it is not a defect.

Hi

Its a big misconception that Developer will change the status of bug. Only Project Manager will decide which bug has to be given 'Deffered' satus and should be fixed later on if required.

Actually after competion all testcases execution tester reports the defect report format to developer. After taking defect format from tester developer did't got why defect was fixed then he put it into dereffered (he nither accept nor reject). He needs strong reson from tester why it made as defect.

A reviewer will be there he may be testing team lead or development team lead. In most of the cases he is development lead only.

Anybody (could be the Developer Dev' Lead Reviewer Release Engineer Test Lead or Test Engineer)will have a right to change the state when it comes to them n it depends on various factors in different situations.

The status depends upon the priority of the bug and the changed person is project manager or Test Lead.