Currently, when using a Checkbox Custom Field on a public form, the checkbox always appears unchecked by default — even if the field’s default value is set to “checked” in the Custom Field settings.

This creates inconsistency between internal task creation and public form submissions. We’d like to request the ability for public forms to honor the default value defined in the field settings. Specifically, if a Checkbox Custom Field has a default value of “checked,” that same default should be reflected on the public form.

Use Case:

We use public forms to collect information from external users. In many cases, we want checkboxes to be pre-checked (e.g., to confirm agreement with terms, pre-select opt-ins, or signal default participation). Right now, users must actively check the box — even though we’ve defined it to be checked by default in ClickUp’s settings.

Expected Behavior:

• When a Checkbox Custom Field is set to “checked” by default, that value should also appear as checked on any public form where the field is used.

• If users choose to uncheck it, their input should override the default as expected.

Why This Matters:

This would allow for more intuitive, consistent form behavior, reduce friction for users, and help ensure accuracy in submitted data — all while aligning with the internal default logic already available within ClickUp tasks.