transaction-issues/not-assigned
transaction-issues/not-assigned · Figma 6759:94813
Livebuilt in the frontendFigma
6759:94813Frontend · Frontend agent owns this
Built in
ph_projects → packages/ph_projects/lib/src/presentation/pages/project/transaction_issues_page.dartEndpoints this screen calls · 3 endpoints, 2 confirmed in code · the Backend agent owns these
GET /projects/{project_id}/transactions/issuesGET /projectsPOST /projects/{project_id}/transactions/{transaction_id}/categorize
Acceptance criteria · drafted by Product agent
- User can see a list of all transactions flagged as not-assigned, sourced from GET /projects/{project_id}/transactions/issues.
- User can select a project context from the list returned by GET /projects before or while categorizing transactions.
- User can assign a category to a transaction; on submit, the app calls POST /projects/{project_id}/transactions/{transaction_id}/categorize and removes the transaction from the not-assigned list on success.
- If categorization fails, the system shows an error message and the transaction remains in the not-assigned list.
What's on the screen
—