cubicweb-seda #14038090 CustodialHistory cardinality [open]

it's currently hard to handle from ma UI POV the 1..n cardinality on CustodialHistory item. What's the rationale this 1..n cardinality in the standard?

Without this, we could handle as for other elements: * keep card specified in the UI for CustodialHistoryItem (CHI) * mark CustodialHistory as required if at least one CHI has a required cardinality

prioritynormal
typebug
done in<not specified>
closed by<not specified>