"Review now" button links to wrong page; design a proper needs-review flow
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- python
- Domain
- full-stack, web-dev
Research direction
Start with ui/templates/dashboard.html around line 165 and trace the dashboard alert and its route handling. Add the auth-gated /review flow, listing the specified uncertain or unrouted transactions with a read-only chat CTA, empty state, dashboard navigation, and synchronized count; verify each acceptance criterion manually.
Written by the indexing model from the issue text.
Description
Bug
The "Review now" button on the dashboard alert banner currently links to /accounts — the bank accounts/balances page. That page has nothing to do with transaction review. Users are dropped somewhere irrelevant with no way to act on the flagged transactions.
Location in code: ui/templates/dashboard.html line ~165
<a href="/accounts" class="btn-secondary btn-sm">Review now</a>
Desired Flow
Philosophy
The real correction workflow lives in MCP/chat — the agent surfaces uncertain transactions, the user replies with the right classification, and the agent calls correct_transaction. The UI's job is to be a lightweight launcher, not a full correction interface.
What the new flow should look like
- Dashboard alert → "Review now" →
/review(new route, or/dashboard?tab=review) - Review page / panel shows:
- Each uncertain/unrouted transaction as a card: merchant, amount, date, current classifier guess, classifier reasoning (uncertainty note)
- Soft visual grouping (e.g. by date or merchant)
- No inline correction form — keep it read-only
- CTA per transaction or at the top: "Review in chat" — opens a pre-filled deep link or copies a ready-made message like: "Please review these transactions: [list]" so the user can paste it into MCP/agent chat and correct via conversation
- Empty state: friendly message when there's nothing to review ("You're all caught up ✓")
Why not a full correction UI?
- Corrections via MCP are more accurate (agent applies rules, learns patterns, creates hints)
- Building a full inline correction form duplicates logic that already lives in the classification engine
- A read-only list + "review in chat" nudge keeps the UI minimal and the MCP loop authoritative
Acceptance Criteria
-
/reviewroute exists and is accessible (auth-gated) - "Review now" button links to
/reviewinstead of/accounts - Page lists all transactions where
uncertain=1ORline_item_id IS NULL, scoped to active user - Each row shows: merchant, amount, date, classifier reasoning (if any)
- "Review in chat" CTA — copies a pre-formatted summary to clipboard (or links to the MCP endpoint)
- Empty state rendered when count is 0
- Nav item or breadcrumb back to dashboard
- Count badge on dashboard alert stays in sync
Out of Scope (for this ticket)
- Inline correction form / dropdowns in the UI
- Rule creation via UI
- Bulk-select / batch correction
- Pagination (handle later if list grows large)
- Dominant language
- Python
- Stars
- 1
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Riddy21/Friday_Budgeting_Pro
-
Contact Hong Opentask
Difficulty 5/5 Over a week Newbie friendliness 1/100
Riddy21/Friday_Budgeting_Pro#353 ·
-
enhancement frontend mobile ui
Difficulty 4/5 3-5 days Newbie friendliness 48/100
Riddy21/Friday_Budgeting_Pro#348 ·
-
enhancement frontend ui
Difficulty 3/5 1-2 days Newbie friendliness 65/100
Riddy21/Friday_Budgeting_Pro#347 ·
-
enhancement frontend ui
Difficulty 4/5 3-5 days Newbie friendliness 52/100
Riddy21/Friday_Budgeting_Pro#346 ·
-
enhancement frontend ui
Difficulty 3/5 1-2 days Newbie friendliness 52/100
Riddy21/Friday_Budgeting_Pro#345 ·
All issues in Riddy21/Friday_Budgeting_Pro
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
bancolombia/sentinel#23 ·
-
test md OpenCI
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
bug client
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100