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.4 KiB
1.4 KiB
id, title, status, date, parent
| id | title | status | date | parent |
|---|---|---|---|---|
| 4-3 | 4-3 Timeline Archiving | QA Review | 2026-09-27 | 4 |
Description
As an admin, I want to archive completed cases and unarchive if needed, So that I can organize active and completed case timelines. Context: Integrates with: timelines table (status field from Story 4.1); Technology: Livewire Volt; Follows pattern: Soft state change pattern. Add these methods to app/Models/Timeline.php:. Full implementation history: docs/stories/story-4.3-timeline-archiving.md
Acceptance Criteria
- Archive button on timeline detail view (admin only)
- Confirmation modal before archiving ("Are you sure?")
- Status changes to 'archived'
- Timeline remains visible to client (read-only as always)
- No further updates can be added (show disabled state with tooltip)
- Visual indicator shows archived status (badge + muted styling)
- Unarchive button on archived timelines
- Status returns to 'active'
- Updates can be added again
- Archiving already-archived timeline: No-op, no error shown
- Unarchiving already-active timeline: No-op, no error shown
- Adding update to archived timeline: Prevented with error message
- Audit log for status changes (action: 'archive' or 'unarchive') - uses AdminLog
actionfield - Bilingual labels (AR/EN for buttons, messages)
- Feature tests covering all scenarios below