Bug Report Guideline
Department
Summary
How Kiluth reports and tracks bugs in Asana: one card per bug batch (e.g. UAT round), each bug as a subtask. Required fields: evidence, steps to reproduce, expected vs actual. Consistent format for UAT, QA, and production bugs.
Table of Contents
Purpose
This guideline defines how Kiluth reports and tracks bugs using Asana. Bugs are grouped into batches (one card per batch), with each individual bug as a subtask.
| Outcome |
|---|
| Consistent, actionable bug reports that include context, evidence, and reproduction steps so Technology can fix issues efficiently. |
Scope
| Included | |
|---|---|
| 1 | Asana card structure for bug batches |
| 2 | Subtask format for individual bugs |
| 3 | Required fields: evidence, steps to reproduce, expected vs actual, notes |
This guideline applies to bugs found during UAT, QA, or production. For UAT workflow and acceptance sign-off, see Client Acceptance (UAT) & Go-Live Guideline.
Where to Create Bug Reports
| Rule | |
|---|---|
| 1 | Create bug batch cards on the Technology board in Asana |
| 2 | 1 card = 1 bug batch (e.g. one UAT round, one release) |
| 3 | Each individual bug is a subtask of the batch card |
Example: Full Bug Batch
Fill all standard Asana fields as usual: priority, dependencies, project/job ID, estimated manhour, etc.
| Asana Card | |
|---|---|
| Title | Fix bugs for Wandee — UAT Round 2 |
| Description | Context • Project/Module: Wandee Web / Checkout + Footer • Environment: UAT (client-facing) • Build/version: v1.8.3 • Reporter: @[Name] (or PM/AE if not yet assigned) Links • Staging/UAT URL: https://uat.wandee.co/checkout • Figma: https://figma.com/file/XXXX (Checkout flow) Subtasks: See below |
Subtask 1
| Field | Content |
|---|---|
| Title | CTA button overlaps footer — Checkout |
| Description | Evidence (annotated) • Screenshot attached: checkout-footer-overlap.png (boxed in red) • Optional recording: https://loom.com/share/XXXX Steps to reproduce 1) Go to https://uat.wandee.co/checkout 2) Scroll to bottom 3) Observe the “Pay now” button area Expected • CTA button sits above footer with 16px spacing and is fully clickable Actual • CTA overlaps footer; bottom 20% is not clickable Notes • Device/Browser: iPhone 13 / iOS 17 / Safari • Happens only on mobile width < 390px |
Subtask 2
| Field | Content |
|---|---|
| Title | Price total mismatch after applying coupon — Checkout |
| Description | Evidence (annotated) • Screenshot attached: coupon-total-mismatch.png (highlight totals) • Console log screenshot attached (no PII) Steps to reproduce 1) Add item A (฿100) + item B (฿200) 2) Apply coupon “SAVE10” 3) Observe total Expected • Total = (100+200) - 10% = ฿270 Actual • Total shows ฿260 (discount applied twice) Notes • Device/Browser: Desktop Chrome • Might be related to recalculation on re-render |
Subtask 3
| Field | Content |
|---|---|
| Title | Error toast covers input label — Login |
| Description | Evidence (annotated) • Screenshot attached: login-toast-cover-label.png (arrow + note) Steps to reproduce 1) Go to /login 2) Submit empty form 3) Observe toast position Expected • Toast appears below header and does not cover form labels Actual • Toast overlays email label, causing confusion Notes • Device/Browser: Desktop Chrome 122 • Repro 100% |
Related
| Document | Purpose |
|---|---|
| Client Acceptance (UAT) & Go-Live Guideline | UAT workflow and acceptance sign-off |
| Asana Usage with Kiluth API | Asana integration and card rules |
| Go-Live & Incident Response Guideline | Go-live execution and incident handling |