Naser Mansour
0f9d12c3cf
Adds docs/tasks/ (16 epics + 102 stories converted to task/subtask files with statuses.md as the new status source of truth) and docs/ux-design.md (retrospective design-system reference), and points CLAUDE.md at them. docs/prd.md and docs/architecture.md are kept as BMAD wrote them; the legacy docs/stories/, docs/epics/, docs/qa/gates/ and .bmad-core/ stay in place as historical/traceability records, superseded but not deleted. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
1.2 KiB
1.2 KiB
id, title, status, date, parent
| id | title | status | date | parent |
|---|---|---|---|---|
| 8-10 | 8-10 Admin Notification - System Events | QA Review | 2026-09-27 | 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