June 26, 2017 at 10:56 am #16556June 29, 2017 at 2:28 pm #16589@jesper-lindholt-ottosenOnly available when logged in
Always direct the reply to a bug back to the person who found it.
good find!July 3, 2017 at 12:28 pm #16614@archanaOnly available when logged in
I agree too.. The person who finds the defect is the one who should be closing itJuly 3, 2017 at 5:36 pm #16622@msalazar18Only available when logged in
Agree! The one that found it, the one that close it! (even thought in practice QA could end up closing bugs submitted for other people o reduce the metrics 😉 )July 7, 2017 at 10:30 am #16658July 10, 2017 at 6:39 am #16666@gedmikriOnly available when logged in
I wouldn’t be so strict with the answer.
The strict rule should be, that reporter, always must be informed about the status of the bug, but sometimes decision to close it could be taken by other project members. From my experience, what we have in our projects:
1) bug is closed by reporter;
2) bug is closed by other team member, who has the same role in the project, as reporter (usually tester). This happens when:
a) lower priority bugs are fixed when reporter is no more a member of the project;
b) reporter needs a help with testing tasks and other team member re-tests fixed bug;
3) bug fix required approval from business, thus fix requires acceptance from their side too. In such a case, bug is closed by business person. These cases are not often, but we not always can avoid while working with of the shelf solution.
4) bug fix price is too high in comparison to the value it has. In such a case, bug might be closed by management (PO, PM, etc.) decision.
You must be logged in to reply to this topic.