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.7 KiB
1.7 KiB
id, title, status, date, parent
| id | title | status | date | parent |
|---|---|---|---|---|
| 2-2 | 2-2 Company/Corporate Client Account Management | QA Review | 2026-09-27 | 2 |
Description
As an admin, I want to create, view, edit, and manage company/corporate client accounts, So that I can serve corporate clients with their unique data requirements. Context: Integrates with: users table (company-specific fields), admin_logs table; Technology: Livewire Volt (class-based), Flux UI forms, Pest tests; Follows pattern: Same CRUD pattern as Story 2.1 Individual Clients. > Note: This migration is NOT part of this story. It is preserved here for future reference if multiple contact persons feature is prioritized. Full implementation history: docs/stories/story-2.2-company-client-account-management.md
Acceptance Criteria
- Form with required fields:
- Validation for all required fields
- Duplicate email/registration number prevention
- Success message on creation
- Display all company clients (user_type = 'company')
- Columns: Company Name, Contact Person, Email, Reg #, Status, Created Date
- Pagination (10/25/50 per page)
- Default sort by created date
- Search by company name, email, or registration number
- Filter by status (active/deactivated/all)
- Real-time search with debounce
- Edit all company information
- Update contact person details
- Validation same as create
- Success message on update
- Display all company information (including contact person details)
- Show consultation history summary
- Show timeline history summary
- Bilingual form labels and messages
- Proper form validation
- Audit log entries for all operations
- Tests for CRUD operations