Secret ingredients to quality software


Dones - Do you know how to do a perfect 'Done' (replying to a bug)?

Last updated by Tiago Araujo on 20 Nov 2018 06:54 pm (over 2 years ago) See History

To reply to a bug effectively and efficiently in your emails, you need to include:

  • Current Status - the bug is fixed (screenshot of working application) or not fixed (ask for more detailed information from the client)
  • Investigation - the reason for the bug, or if you don't know, what you investigated, e.g. checked Windows event logs and found nothing helpful
  • Solution - how you fixed the bug (code snippet if necessary)

better emails reply bug small
Figure: Good Example - Reply to a bug showing all steps

Adam CoganAdam Cogan
Cameron ShawCameron Shaw

We open source. This page is on GitHub