DDovel Team
CockpitOverview & what needs youChatAsk the Product agentFigma SyncLive diff vs the PRDFeaturesEvery feature & its specFlowsAI-inferred from the designs✓BacklogWhat's left to buildScreensPages, specs & criteriaRoadmapNew in Figma → proposalsDriftWhat changed in designMeetingsCalls → decisions → PRDTeamPeople + their AI support
Figma Dovel iQ v0.3 MVP (Active) · 2026-10-10
Dovel Team
PProduct agentsupports Design & PM✓BBackend agentsupports EchecomingFFrontend agentsupports the FE buildcomingQQA agentsupports QualitycomingOOrchestrator agentsupports Opscoming
Flows / Resolve transaction issues / duplicate-transaction

duplicate-transaction

duplicate-transaction · Figma 6759:95384

duplicate-transaction
Scopednot in the frontend yetFigma 6759:95384

Frontend

No matching Flutter page yet — not built.

Endpoints this screen calls · 2 endpoints, 0 confirmed in code · the Backend agent owns these

GET /projects/{project_id}/transactions/{transaction_id}POST /projects/{project_id}/transactions/{transaction_id}/resolve-duplicate

Acceptance criteria · drafted by Product agent

  • User can view full details of the flagged transaction via GET /projects/{project_id}/transactions/{transaction_id}, including the duplicate counterpart it conflicts with.
  • User can choose a resolution option (e.g., keep this transaction, keep the duplicate, or merge) before submitting.
  • On submit, the app calls POST /projects/{project_id}/transactions/{transaction_id}/resolve-duplicate with the chosen resolution and shows a success confirmation.
  • On success, the transaction is removed from the duplicate issues list and the user is returned to the issues overview.

What's on the screen

—
P
Product agent
supports Design & PM
×