Q. How can I make a useful bug report?
A. Please provide the info up front. Programmers don't mind
being told "something obvious" about your environment - eg I am using Windows.
Every problem report should include:
Title - I suggest something neutral here, rather than saying "bug" or "failure" use "issue", etc.
Environment - Don't make the programmer ask or assume
Steps to reproduce
Expected Result - even if its obvious (eg should not crash)
Visual Proof (screenshots, videos, text) - include URL if relevant
If the program in question runs things (eg a web browser) its best to
provide a *minimal* example of the html that causes the issue - not your whole website.