3 ms·

How to help your team write better bug reports

• maxcameron 16y ago
  I didn't write this for customers obviously - they deserve to report bugs in any way they want. But I think developers need to do a better job helping their team-members write better bug reports.
• camwest 16y ago
  Max and I had a conversation about this piece and one thing we wanted to avoid was pigeonholing our bug reports into a category system like I've seen so many others do: Fill out 15 drop downs to describe the state of your machine when the bug was found. What component, what OS, browser etc… There has to be a better way than that right?
• Isamu 16y ago
  Add a bug button on the prototype? Integrating the bug reporting means you can automatically supply a history of the last n things the user did, or whatever debugging state you think is helpful, and the user will fill in the rest. Similar to automatic crash reporting, except without requiring the crash.
  • camwest 16y ago
    This is a great idea. I wonder how much state information we would have to track for this to be useful.
    • maxcameron 16y ago
      This is cool. But it wouldn't really help our internal team "understand" the bug in question - if that's important.
      • Isamu 16y ago
        The bug button pops up the usual form for the user to fill out - describe the bug, etc. It's just that more extensive state can be silently added to help recreate the bug, or at least provide the context that is often missing.