Naser Mansour
7f35297025
Naser confirmed all remaining QA Review / Draft rows (97 subtasks, 16
parent rollups) are done in substance: the site has been in production
for roughly a year. Overrides the conservative QA-Review/Draft mapping
from the prior takeover commit (0f9d12c) at his explicit instruction.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
28 lines
1.2 KiB
Markdown
28 lines
1.2 KiB
Markdown
---
|
|
id: 8-10
|
|
title: 8-10 Admin Notification - System Events
|
|
status: Done
|
|
date: 2026-09-27
|
|
parent: 8
|
|
---
|
|
|
|
## Description
|
|
|
|
As an admin, I want to be notified of critical system events, So that I can address issues promptly. - app/Notifications/SystemErrorNotification.php - app/Notifications/QueueFailureNotification.php - app/Contracts/ShouldNotifyAdmin.php (marker interface) - app/Services/AdminNotificationService.php (rate limiting logic). Full implementation history: docs/stories/story-8.10-admin-notification-system-events.md
|
|
|
|
## Acceptance Criteria
|
|
|
|
- [ ] Email delivery failures (SMTP errors, bounces)
|
|
- [ ] Scheduled job failures (Laravel scheduler)
|
|
- [ ] Queue job failures
|
|
- [ ] Critical application errors (database, payment, etc.)
|
|
- [ ] Event type and description
|
|
- [ ] Timestamp (formatted per locale)
|
|
- [ ] Relevant details (error message, stack trace summary, job name)
|
|
- [ ] Recommended action (if applicable)
|
|
- [ ] Environment indicator (production/staging)
|
|
- [ ] Sent immediately using sync mail driver (not queued)
|
|
- [ ] Clear subject line indicating urgency with event type
|
|
- [ ] Rate limited: max 1 notification per error type per 15 minutes
|
|
- [ ] Uses base email template from Story 8.1
|