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.0 KiB
1.0 KiB
id, title, status, date, parent
| id | title | status | date | parent |
|---|---|---|---|---|
| 4-5 | 4-5 Client Timeline View | QA Review | 2026-09-27 | 4 |
Description
As a client, I want to view my case timelines and updates, So that I can track the progress of my legal matters. Context: Integrates with: timelines, timeline_updates tables; Technology: Livewire Volt (read-only); Follows pattern: Client dashboard pattern. Full implementation history: docs/stories/story-4.5-client-timeline-view.md
Acceptance Criteria
- Display all client's timelines
- Active timelines prominently displayed
- Archived timelines clearly separated
- Visual distinction (color/icon) for status
- Show for each:
- Case name and reference
- Status indicator
- All updates in chronological order
- Each update shows:
- Read-only (no edit/comment)
- No ability to archive/delete
- Only see own timelines (403 for unauthorized access)
- Recent updates indicator (new since last view, optional)
- Responsive design for mobile
- Bilingual labels and dates