How To Write An Effective Bug Report

Bug Report: Bug report is a very important aspect of software testing which is mainly use to document an issue. 
in this our main focus to describe an issue such type that it would be easy to understand and also easy to reproduce.
an effective bug report should have following things:

1. Bug Title : The title of a bug report should seeking to describe. once anyone read it should get an idea what is it about. 
It should be short in length but descriptive in words.

2. Priority : We decide the the priority of an issue on the basis of how much this issue impact on our business. 
may be an issue is not much effected to our functionality but it play a major role for our business. then we need to set it's in high priority.

3. Component/Module : If we get any issue we need to mention that in which particular module or component we are getting this issue. 
so that it should be much easy to replicate the issue without going into entire application. It also helpful for developers to fix an issue for the particular component.

4. Assignee : In this field we need to assign the issue to a concerned person who will be taking care further.

5. Platform : In this field we need to mention the platform where you found the issue.

6. Description : Here we need to describe the issue and try to explain what exactly going on. It should be enough informative and clear. It should have following fields:
a. Steps to reproduce
b. User credentials 
c. System information
d. Expected result
e. Actual result
 
7. Screenshot : We should attach a screenshot in bug report if the bug is little bit complicated. this is the best way to share the screenshot.

8. Severity : it means how effective the bug as per the functionality point of view. It plays a major role to decide how soon the bug should get fix.

Regards,