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>
31 lines
1.1 KiB
Markdown
31 lines
1.1 KiB
Markdown
---
|
|
id: 4-6
|
|
title: 4-6 Timeline Update Notifications
|
|
status: Done
|
|
date: 2026-09-27
|
|
parent: 4
|
|
---
|
|
|
|
## Description
|
|
|
|
As a client, I want to receive email notifications when my timeline is updated, So that I stay informed about my case progress without checking the portal. Context: Integrates with: timeline_updates creation, email system; Technology: Laravel Notifications, queued emails; Follows pattern: Event-driven notification pattern. Full implementation history: docs/stories/story-4.6-timeline-update-notifications.md
|
|
|
|
## Acceptance Criteria
|
|
|
|
- [ ] Email sent when new update added to timeline
|
|
- [ ] Triggered automatically on TimelineUpdate creation
|
|
- [ ] Queued for performance
|
|
- [ ] Case name and reference
|
|
- [ ] Update summary or full text
|
|
- [ ] Date of update
|
|
- [ ] Link to view timeline
|
|
- [ ] Libra branding
|
|
- [ ] Email in client's preferred language
|
|
- [ ] Arabic template
|
|
- [ ] English template
|
|
- [ ] No email for archived timeline reactivation
|
|
- [ ] No email if client deactivated
|
|
- [ ] Professional email template
|
|
- [ ] Tests for notification sending
|
|
- [ ] Error handling for failed sends
|