Fictional case study · Document 15 · Week 8; resolved in week 10
Issue Log
The team tracks the duplicate-event defect, its owner, actions and resolution.
Illustrative project record. AegisShield, BookEasy, the people, decisions and outcomes are fictional.
Issue ISS-01
| Field | Record |
|---|---|
| Detected | Week 8 during staging integration tests |
| Related risk and requirement | R03 — missing or duplicate events; REQ-03 — retain event ID and suppress duplicates in agreed scenarios |
| Description | When a test request succeeds but the response times out, a retry uses a new identifier and the same event can be processed twice. |
| Impact | Duplicate stored test events can produce repeated alerts. The BookEasy pilot is blocked until the fix passes retesting. |
| Owner | Engineering lead; backend engineer implements the correction and QA verifies it |
| Initial status | Open in week 8; no production incident or customer data loss established |
Action and resolution
| When | Action / outcome | Owner |
|---|---|---|
| Week 8 | Reproduce the timeout scenario and trace the identifier change. | Engineering / QA |
| Weeks 9–10 | Preserve the original event ID across retries; review failure monitoring and add timeout and duplicate tests. | Backend / DevOps / QA |
| Week 10 | QA reruns the agreed scenarios; the original test defect no longer reproduces and the issue is closed for the pilot. | QA / Engineering lead |
Follow-up
The PM links ISS-01 to the schedule decision, reports progress to the sponsor and coordinates customer communication. The result applies to the agreed test scenarios, not every possible failure condition.
Current status and tracking
Current status: Closed. Closure date: March 13, 2026 (simulated). Priority: High. Target resolution: March 13, 2026. GitHub board reference: github-board-during.md, ISS-01 card. The issue was Open in week 8; that is historical status, not the current status.
Cause, correction and closure evidence
Root cause: when the response timed out, the retry created a new event identifier. Correction: preserve the original event ID and check processed-event records before writing so the same event is processed once. QA retested the timeout, retry, duplicate, and normal-delivery scenarios in week 10. Engineering lead verified the correction, QA recorded the passing results, and the PM accepted the closure evidence against REQ-03. Key terms with case examples: Issue is a current problem that needs action, such as ISS-01 blocking the pilot. Defect is behavior that fails an expected result, such as one event being processed twice. Root cause is why it happened, such as the retry creating a new ID. Retest means repeating the failed scenario after correction. Closure evidence is proof such as passing logs, duplicate checks, and QA results linked to REQ-03.