Usability - Required relations should not offer a "None" option
Bug #513142 reported by
Oded Peer
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | ||
|---|---|---|---|---|---|---|
| play framework | Status tracked in 1.0 | |||||
| 1.0 |
Fix Released
|
Undecided
|
Unassigned | |||
| 1.1 |
Fix Committed
|
Undecided
|
Unassigned | |||
Bug Description
Suppose I have a "Thing" and a "DependantThing" model objects.
"DependantThing" has a required many to one relation to "Thing" (many DependantThings to a Thing).
The CRUD module offers a default "None" value in the "create DependantThing" page, which is wrong.
In case we don't have any "Thing" objects and the user tries to create a "DependantThing" he should get an error message
Revision history for this message
| Oded Peer (oded-50) wrote | #1 |
To post a comment you must log in.
