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.3 KiB
1.3 KiB
id, title, status, date, parent
| id | title | status | date | parent |
|---|---|---|---|---|
| 6-6 | 6-6 Data Export - Timeline Reports | QA Review | 2026-09-27 | 6 |
Description
As an admin, I want to export timeline and case data, So that I can maintain records and generate case reports. Context: Follows pattern: Story 6.4 (User Lists Export) and Story 6.5 (Consultation Export) - same UI layout, filter approach, and export mechanisms; Integrates with: Timeline model, TimelineUpdate model, User model; Technology: Livewire Volt, Flux UI, league/csv, barryvdh/laravel-dompdf. Full implementation history: docs/stories/story-6.6-data-export-timeline-reports.md
Acceptance Criteria
- Export all timelines (across all clients)
- Export timelines for specific client (client selector/search)
- Status filter (active/archived/all)
- Date range filter (created_at)
- Client filter (search by name/email)
- Case name and reference
- Client name
- Status
- Created date
- Number of updates
- Last update date
- CSV format with bilingual headers
- PDF format with Libra branding
- Include update content toggle (full content vs summary only)
- When enabled, PDF includes all update entries per timeline
- Filter controls match Story 6.4/6.5 layout
- Export buttons clearly visible
- Loading state during export generation
- Success/error feedback messages