Defect template or Bug template

Defect template is also known as Bug template.The defect reporting template has some list of attributes or columns names some which are mandatory. 

Defect template or Bug template may vary as per organization to organization. Below are the most common attributes used in defect template.

1.  Defect ID: In order to refer and access the specific defect easily, quickly and uniquely. The unique id is provided to the defect is called Defect ID.

2.   Defect Description: This section describes the issue with more clarity and details.

3.    Summary: This describes the description of the defect.

4.    Steps to reproduce: This section describes the steps to reproduce the identified defect. It provides the details in step wise.

5.    Test Case: It is the unique Id for each test case or step. In order to identify and access the test case easily whenever it is required. In ideal tester marks the particular test step of test case as failed and link the identified defect to the test case or test step.

6.    Actual result: The current issue description

7.     Expected result: The behaviour of application which is expected

8.     Module name: It contains the name of the module in which issue is encountered.

9.      Detected By: The name of the tester who has identified the issue. By default, It displays the name of the person who logged the defect in to the QC.

10.   Release name: The name of the release in which issue is identified.

11.   Build name: It contains the version of the released build.

12.   Project: It defines the name of the project in which issue is encountered.

13.   Priority: The Priority order or sequence in which defect should get resolved

14.   Severity: The Severity defines the impact of the defect on the system or application.

15.   Status: It contains the status of the raised defect.

16.   Assigned To: This describes the person who should be looking in to the issue.

17.   Detected on: The date on which defect is identified and raised.

18.   Remarks: It describes the status of the raised defect such as reason for failure.

Note: Some project might have more or different field name in Defect template or Bug template depending on the requirement.
E.g. Few projects might have just Severity field not the Priority field.