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 |
|---|---|---|---|---|
| 2-3 | 2-3 Account Type Conversion | QA Review | 2026-09-27 | 2 |
Description
As an admin, I want to convert individual accounts to company accounts and vice versa, So that I can accommodate clients whose business structure changes. Context: Integrates with: Users table, consultations, timelines; Technology: Livewire Volt (class-based), Flux UI modals, Pest tests; Follows pattern: Admin action pattern with confirmation modal (same as Story 2.1/2.2 CRUD pattern). Full implementation history: docs/stories/story-2.3-account-type-conversion.md
Acceptance Criteria
- "Convert to Company" action available on individual profiles
- Modal/form prompts for additional company fields:
- Preserve existing data (email, phone, password)
- Preserve all consultation history
- Preserve all timeline history
- Confirmation dialog before conversion
- Success message after conversion
- "Convert to Individual" action available on company profiles
- Modal/form prompts for individual-specific fields:
- Handle company-specific data:
- Preserve all consultation history
- Preserve all timeline history
- Confirmation dialog before conversion
- Audit log entry capturing:
- Email notification to user about account type change
- Bilingual confirmation dialogs
- Bilingual email notification
- All data preserved (verify in tests)
- No broken relationships after conversion