locked
Recommended workflow for dealing with crash events RRS feed

  • Question

  • We are currently trying to adopt Windows Error Reporting. Now we are facing the question how to manage the incoming events.

    The main difficulty I see is that we cannot tick a checkbox or add an internal comment for each event to document that it is being dealt with. Of course we would open a tickets in our bug tracking system for every event with existing cabs and/or with a certain minimum hit count, so we can tell for each event if a ticket exists for it with a search in the bug tracking system. But it would be much more efficient, if I could do the inverse by attaching a link to our BTS for every WER event we already looked at.

    We don't want to invest too much effort into automation (automated download via webservices etc.), at least not until we are sure that we will continue using WER.

    Does anyone have some good and practicable ideas for us how to keep track of the icoming events without much effort..?

    • Moved by Max Wang_1983 Tuesday, April 26, 2011 1:22 AM forum consolidation (From:Windows Error Reporting for ISVs)
    Tuesday, November 2, 2010 4:33 PM