"Review now" button links to wrong page; design a proper needs-review flow

Open
#337 1 comment 0 reactions 0 assignees View on GitHub

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

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 enhancement ux

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
  1. Dashboard alert → "Review now" → /review (new route, or /dashboard?tab=review)
  2. 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
  3. 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
  4. 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

  • /review route exists and is accessible (auth-gated)
  • "Review now" button links to /review instead of /accounts
  • Page lists all transactions where uncertain=1 OR line_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

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Riddy21/Friday_Budgeting_Pro

All issues in Riddy21/Friday_Budgeting_Pro

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.