Purpose
The purpose of this template is to standardize how defects and issues are reported across projects at Memorres. Defects that lack details, evidence, or structure waste developer time, frustrate PMs, and create friction between teams. This template ensures that every defect is logged with sufficient information to be reproducible, traceable, and actionable. By using a uniform structure, lean QA teams can minimize back-and-forth clarifications and focus on resolution.
Scope
This template is to be used by all QA Engineers and QA Leads when logging defects during test execution, regression, or integration testing. It applies to SaaS, web, and mobile projects and must be maintained in the approved bug tracking tool. It excludes production incidents reported by clients, which follow a different incident reporting process.
Bug Report Template
| Field | Description | Example Entry |
| Bug ID | Auto-generated or manually assigned unique identifier | DEF-102 |
| Title | Concise description of issue (module + observed error) | “Login error 500 after submitting valid credentials” |
| Environment | Where the defect occurred (staging, pre-prod, device/browser) | Staging v1.2.3 – Chrome 118 on Windows 11 |
| Build/Version | Build number or commit ID where defect observed | Build #145 – Commit ab12cd |
| Steps to Reproduce | Step-by-step actions leading to issue | 1. Open staging URL → 2. Enter valid credentials → 3. Click submit → 4. Error 500 displayed |
| Expected Result | What should have happened based on requirement/acceptance criteria | User redirected to dashboard with active session |
| Actual Result | What actually happened | Error 500, blank page |
| Severity | Impact on system (Critical, Major, Minor, Trivial) | Critical |
| Priority | Order of fix (High, Medium, Low) set in collaboration with PM/Dev Lead | High |
| Attachments | Screenshots, logs, video recordings if needed | Screenshot of error + console log |
| Assigned To | Developer or team responsible | Dev User A |
| Status | Lifecycle stage (New, Assigned, In Progress, Fixed, Retest, Closed, Reopened) | New |
Issue Log Template (Summary View)
For tracking defects at a project level, QA Leads maintain a log summarizing key defect details:
| Bug ID | Title | Severity | Priority | Assigned To | Current Status | Date Logged | Date Closed |
| DEF-102 | Login error 500 on staging | Critical | High | Dev A | In Progress | 12 Sept | – |
| DEF-103 | Checkout button misaligned | Minor | Low | Dev B | Closed | 13 Sept | 14 Sept |
| DEF-104 | Password reset link expired early | Major | Medium | Dev A | Retest | 14 Sept | – |
Closing Note & Cross-References
This template ensures that every defect reported at Memorres is complete, actionable, and traceable. By capturing detailed reproduction steps, evidence, and lifecycle status, the template reduces disputes, accelerates fixes, and creates an auditable record of quality assurance.
It should always be used alongside the How-To – Logging & Prioritizing Defects Correctly, which explains execution discipline, and the Test Execution & Bug Lifecycle Management SOP, which governs defect transitions.