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 |
|---|---|---|---|---|
| 3-5 | 3-5 Admin Booking Review & Approval | QA Review | 2026-09-27 | 3 |
Description
As an admin, I want to review, categorize, and approve or reject booking requests, So that I can manage my consultation schedule and set appropriate consultation types. Context: Integrates with: consultations table, notifications, .ics generation; Technology: Livewire Volt, Flux UI; Follows pattern: Admin action workflow. Create these notification classes in app/Notifications/:. Full implementation history: docs/stories/story-3.5-admin-booking-review-approval.md
Acceptance Criteria
- View all pending booking requests
- Display: client name, requested date/time, submission date
- Show problem summary preview
- Click to view full details
- Sort by date (oldest first default)
- Filter by date range
- Full client information
- Complete problem summary
- Client consultation history
- Requested date and time
- Set consultation type:
- If paid: set payment amount
- If paid: add payment instructions (optional)
- Approve button with confirmation
- On approval:
- Optional rejection reason field
- Reject button with confirmation
- On rejection:
- Quick approve (free) button on list
- Quick reject button on list
- Bulk actions (optional)
- Audit log for all decisions
- Bilingual notifications
- Tests for approval/rejection flow