UI Design - Transfers (Bill of Sale - Transfer Details Updates - Declared Value / Consideration Value)
- Dominant language
- JavaScript
- Stars
- 23
- Forks
- 62
- Avg merge
- 24m
- Merged PRs (30d)
- 1
Description
**Issue:**
The issue stems from confusion between the declared value and the consideration amount, which impacts the recorded 'market value' of the home. To help resolve this, we’d like to provide as much context as possible to minimize errors and confusion.
**Note: The Declared Value** should be the current market value of the home, which will be the consideration paid by an arms length purchaser to a seller as indicated on the **_bill of sale_**, or the **_estimated market value_** if the length if the sale is not at arm's length, that was the.
**Suggest:**
- Move Transfer details below 'Declared Value' so users can easily see and compare the content of the two fields
- add (i) information tool tips to the Declared Value and Consideration Amount (policy to provide conten)
- Functionality: When user selects a Bill of Sale transfer type, show declared value, consideration amount, and Bill of Sale date of execution.
### **[Figma Design](https://www.figma.com/design/YcXMXw581zx7YxR34gkKvs/MHR-Transfers?node-id=5587-14632)**
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the existing Transfers UI and compare it with the linked Figma design, focusing on the Bill of Sale transfer type and the Declared Value and Consideration Amount fields. Done means Transfer details appears below Declared Value, both value fields have the requested information tooltips, and the Bill of Sale date of execution is shown for that transfer type.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- design, frontend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100