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 |
|---|---|---|---|---|
| 4-1 | 4-1 Timeline Creation | QA Review | 2026-09-27 | 4 |
Description
As an admin, I want to create case timelines for clients, So that I can track and communicate progress on their legal matters. Context: Integrates with: timelines table, timeline_updates table, users table, admin_logs table; Technology: Livewire Volt, Flux UI; Follows pattern: Admin CRUD pattern (see existing admin components). Full implementation history: docs/stories/story-4.1-timeline-creation.md
Acceptance Criteria
- Select client (search by name/email) - only users with user_type 'individual' or 'company'
- Case name/title (required)
- Case reference number (optional, unique if provided)
- Initial notes (optional)
- Timeline assigned to selected client
- Creation date automatically recorded
- Status defaults to 'active'
- Can create multiple timelines per client
- Confirmation message on successful creation
- Timeline immediately visible to client
- Case name required
- Case reference unique if provided
- Client must exist
- Audit log entry created via AdminLog model
- Bilingual labels and messages
- Tests for creation flow