Skip to content

Mandatory state of a Selection Yes/No column #2337

@michiey

Description

@michiey

Is your feature request related to a problem? Please describe.

Sometimes it is desirable or could be helpful to have a Selection Yes/No Column mandatory to be changed in a view, for example to flag a row as already processed or flag a client as registered.

Right now, even if a Selection Yes/No Column is set as mandatory the default state is accepted as, of course, a default Yes or No is already a perfectly fine value in itself. Nevertheless this preventes having this kind of columns as mandatory at all.

Describe the solution you'd like

If a Selection Yes/No Column is set as mandatory in a view, only the non-default state should be accepted to be able to save this row.

Describe alternatives you've considered

No response

Additional context

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    0. Needs triagePending approval or rejection. This issue is pending approval.enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions