What is the company process or procedure? Who is responsible for changing the status of a defect? Who approves the status of rejected? In this case they have been identified as "valid". Who makes the final determination on what is a valid reason?
Sure, QA does it in some places, a Change Control Board or the PM could also be the one to do it.
I think it needs to have its status changed. After a defect is rejected, the person that filed it must acknowledge that it is indeed *not* a defect. if a large number of defects are labeled as "rejected", how would you ever know which were rejected for valid reasons and which ones need to be resubmitted?
Thanks for answering my question but i did not get my answer yet. the question is should the rejected defects be changed to closed once it is determined that they are not defects or should they be left as Rejected with a comment giving the reason for rejection.
The answer depends on your defect tracking tool.
If your defect tracking tool allows you to know the defect type/category(as rejected) even after closing the defect,then you can very well close the rejected defect.Because you can still get the report or count of valid and invalid defects.
Otherwise, if after closing the defect,there is no means to know whether it is a valid or invalid defect,then it is better to leave the rejected defect as open( for reporting and defect analysis purpose.)
The person to close the defect is the one who raised it ,basically the tester.
I also would say..it depends on the company procedures whether to close it or keep it as it is.
In our case the group (Func spec,Devl and teaters) discuss the reason why it is rejected and what would be the concequences if it has to be rejected. If the reasons are worth then the bug would be closed. At any point of time we know which bugs are rejected.
According to me, QA should give the defect closure comments irrespective of the bug status whether it is closed or not reproducible or NAB (Not a Bug)or rejected or fixed. I feel it should come to tester queue to address the defect. It will be useful later to analyze defect closure rate or reporting etc.