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>
30 lines
1.2 KiB
Markdown
30 lines
1.2 KiB
Markdown
---
|
|
id: 8-8
|
|
title: 8-8 Timeline Update Notification
|
|
status: QA Review
|
|
date: 2026-09-27
|
|
parent: 8
|
|
---
|
|
|
|
## Description
|
|
|
|
As a client, I want to be notified via email when my case timeline is updated, So that I stay informed about my case progress without having to repeatedly check the portal. Full implementation history: docs/stories/story-8.8-timeline-update-notification.md
|
|
|
|
## Acceptance Criteria
|
|
|
|
- [ ] Email sent automatically when `TimelineUpdate` is created
|
|
- [ ] Uses model observer pattern for clean separation
|
|
- [ ] Email queued for performance (not sent synchronously)
|
|
- [ ] Only triggered for active timelines (not archived)
|
|
- [ ] Subject: "Update on your case: [Case Name]" / "تحديث على قضيتك: [اسم القضية]"
|
|
- [ ] Case reference number (if exists)
|
|
- [ ] Full update content text
|
|
- [ ] Date of update (formatted for locale)
|
|
- [ ] "View Timeline" button linking to client dashboard timeline view
|
|
- [ ] Email template selected based on client's `preferred_language`
|
|
- [ ] Default to Arabic ('ar') if no preference set
|
|
- [ ] Date formatting appropriate for locale
|
|
- [ ] Uses base email template from Story 8.1 (Libra branding)
|
|
- [ ] Professional, informative tone
|
|
- [ ] Clear visual hierarchy: case name → update content → action button
|