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>
34 lines
1.3 KiB
Markdown
34 lines
1.3 KiB
Markdown
---
|
|
id: 6-6
|
|
title: 6-6 Data Export - Timeline Reports
|
|
status: Done
|
|
date: 2026-09-27
|
|
parent: 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
|