| Sr. No. | Type | Title | Description/Summary | Screenshot | Steps to Reproduce | Status | Priority | Resolution | Assignee | Reporter | Created |
|---|---|---|---|---|---|---|---|---|---|---|---|
| How to fill in the template |
|---|
1
Bug
2
Clarification
3
Bug
4
Bug
5
Bug
6
Change Request
7
Bug
8
Bug
9
Change Request
10
Bug
Title: Enter a clear title for the bug, so anyone, regardless of role, can understand it (e.g., “Invoice Will Not Print for User”).
Description/Summary: In addition to a clear title, add an easy-to-understand description of the bug (e.g., “The invoice will not print for the user when they have the invoice opened and click the Print button”).
Environment: Include any environment details (such as browser, operating system [OS], URL, software version, etc.), so anyone reviewing the bug can easily glean the environmental factors, and so development can replicate the bug and fix it.
Screenshot: Add a screenshot of the bug, if applicable. That way, whatever the software malfunction, the issue will be clear to anyone reviewing the report.
Steps to Reproduce: Include the exact steps you take to reproduce the bug occurrence (e.g., “Customer running Windows 10 and Internet Explorer 8 cannot print an invoice”).
Status: Specify the status of the bug using the Status dropdown list (e.g., new, open, resolved, accepted, in progress, to be validated, done, etc.).
Priority: Select a priority for the bug using the Priority dropdown list (e.g., critical, high, medium, low, etc.).
Resolution: Select the bug’s status using the Resolution dropdown list (e.g., unresolved, fixed, etc.).
Assignee: Enter the name of the employee who is responsible for ensuring that the bug is fixed.
Reporter: Enter the name of the person who reported the bug.
Created: Enter the date that the bug was reported.