We have already discussed the elements of a good bug report. Here are a few more things to keep when doing it:

• Tip 1: Be sure your bug is reproducible
  

  Sometimes the bug you find isn’t really a bug. It is just a temporary glitch that was caused by a rare and temporary condition in your environment. In that case, it will be hard for the developer to figure out what is going on and to fix it.
  That’s why you have to reproduce it. Experts suggest you should try it several times. If the unwanted result happens only sometimes, you can still file a bug, but you must mention that its appearance is sporadic.

• Tip 2: Has this bug already been reported?
  

  If you are not the only tester for the application, there is always a chance that the bug you just found has already been raised. Don’t duplicate; you will be wasting everybody’s time.

• Tip 3: Report the bug right away
  

  Don’t wait to report it when you find a bug. If you decide to write the bug report later, you will more likely forget to mention some crucial elements in your message.

•  Tip 4: Be specific, clear, and brief
  

  Developers need to read dozens or even hundreds of such reports every day, and they hate reading long essays containing irrelevant data. So try to evaluate what is relevant and write short, clear sentences.

• Tip 5: Test in multiple environments if you expect it to be an environment issue.

  Some bugs occur just in specific environments, so it is good to be as specific as possible. Make sure to list the operating system or browser you are using, and if applicable, which version of software and hardware you are using. If you can, help out the developer by testing on multiple environments to see if the bug is present in multiple environments or not.

• Tip 6:Leave your opinions out of your report
  

  Unless you submit a feature request or you are really sure what the cause of the bug is, you should stick to the facts and avoid suggesting how to fix a bug or what is causing it.

• Tip 7: Avoid the criticism
  

  It’s hard enough for developers to find out they made a mistake. Discouraging language doesn’t help – either for the relationship or the further work that has to be done.

• Tip 8: Screenshot/screencast
  

  Make good screenshots and highlight the areas to draw attention to the right stuff. Sometimes even a short video is useful because it’s easier than reading, and the developer can get a clearer picture of what is going on. Some excellent tools are available for making this kind of screenshots and screencasts (like ShareX, Peek, LiceCap, etc.).

• Tip 9: your bug report before you send it
  

  Read everything you wrote and be aware of the language. Is it clear? Did you put in all the necessary information? Did you misspell any words or use sentences that could be misinterpreted in any way? Make sure they don’t have multiple meanings.

• Tip 10: Remain available after filing the report
  

  Developers often need additional information about the bug, so it’s essential to remain available after you’ve done the report.

• Tip 11: Ask developers if your bug reports are ok
  

  You’ll get better and better at reporting. That comes with practice. Ask for developers’ feedback! Do they miss anything in your reports in general? Is there something you could do better? Your teammates will be pleasantly surprised and will appreciate your concern.
  And you will learn something new!

Conclusion:

It really pays off to follow these practices. The issues you raise will be resolved sooner and more effectively. In return, you’ll enjoy a good reputation among fellow developers.

You can read more about writing a bug report here.