one2many handling of defaults not intuitive
Registered by
Ferdinand
see also https:/
if the user clicks on "New" one2many and all fields in the new resource are suplied as default values - no manual interaction is necessary - but save does not save the new record. It requires the user to delete and reenter at least one of the default values.
I still think it's a shortcoming in design.
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- None
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- Superseded
- Series goal:
- None
- Implementation:
-
Implemented
- Milestone target:
- None
- Started by
- Fabien (Open ERP)
- Completed by
- Fabien (Open ERP)
Related branches
Related bugs
Sprints
Whiteboard
(?)
