• Author
  • #16556

    Just came across an interesting post Who Closes out the Defect Report from Mike Jennings where he discussed about life cycle of Bug report and who should be the one to close out a bug/ defect report.


    Always direct the reply to a bug back to the person who found it.

    good find!


    I agree too.. The person who finds the defect is the one who should be closing it


    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 ­čśë )


    @msalazar18 Either QA or PM would be closing out bugs from other people ­čÖé



    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.


    Ideally the person who raised the defect/bug or someone within that team.  There also, needs to be good information/evidence on why you are closing the defect.

Viewing 7 posts - 1 through 7 (of 7 total)

You must be logged in to reply to this topic.