Following are the do’s for a good bug report :

• When you're finished, read your report. Make sure it's clear, concise, and SIMPLE to understand.
• Don't allow any opportunity for ambiguity by being as clear as possible.
• Do TEST the problem a few times to see if there are any superfluous procedures.
• Include any workarounds or additional procedures you've discovered that cause the problem to behave differently in your report.
• Check to see if the bug has previously been reported. If it has, please leave a comment on the bug with your information.
• Do reply to requests for further information from developers.

Following are the don’ts for a good bug report :

• DO NOT submit a report that contains more than one bug. When there are numerous bugs in the report, keeping track of their progress and dependencies becomes difficult.
• DO NOT be judgmental or accusatory. Bugs are unavoidable, yet they aren't always simple to fix.
• DO NOT try to figure out what's causing the bug. Stick to the facts to avoid sending the developer on a wild goose hunt.
• Anything that isn't a bug should be posted. Developers appreciate hearing from you, but sending information to the wrong channel will just block their WORKFLOW and cause DELAYS.