The template of the bug report depends on the bug tracking system you use. Usually the bug report should contain the following fields:
- unique identifier
- build version
- summary
- description
- step to reproduction
- reproduction (always, sometimes)
- severity
- priority
- symptom
As soon as a bug has been found, it must be reported because you can forget about the bug. Do not prepare the report on a paper (you can lose it) and log the report to the bug tracking system. These are simple rules but many testers neglect them and many bugs have been left unfixed.
Practical Tips on Software Testing 
Comments on: "How to create a good bug report" (5)
Eric Rayburn posted:
The article is an excellent source of informing the tester or the many types of way to identify and fix bug problems. I intend I incorporating these tactics in my work.
@Eric Rayburn
Thank you! I’m glad that you like the article.
Hello, this is a good write-up. You receive my vote for How to create a good bug report Practical Tips on Software Testing and also I am going to bookmark this blog now.
@Bile
Thanks 🙂 We have already prepared a few interesting articles, and soon we are going to publish them.
Hello,I like to read more on this field. Thank you for publishing How to create a good bug report Practical Tips on Software Testing.