Custom checkbox fields and setting required fields don't work

Question

So we have two checkboxes in our JPD space, which we require for people when adding new ideas. However, the current implementation only allows the checkbox to be checked for it to be considered filled it. However in my view not checking a checkbox is also filling it, but with the state off. At this point you can't really use checkboxes if you also want to make the other fields mandatory. So you either have to replace the checkbox with the less ui-friendly selectbox with yes and no in it.

Is there another way to accomplish what we want and that is to use checkboxes in our view which we also use for creating new ideas?

Olha Yevdokymova_SaaSJet · Answer

Hi @André

Christos explained the native limits well. An unchecked checkbox counts as empty, and “mandatory” on the JPD create form is all or nothing.

Since you asked for other options, another approach you might consider is Smart Forms for Jira (developed by my team). It handles idea intake with its own form builder:

* Required per field: make only the fields you need mandatory, instead of all or nothing.
* Use the element that fits: a checkbox for optional confirmations, and a Yes/No choice when “No” must count as a real answer.
* Map answers to your JPD fields, so ideas are created with the values already filled in.
* Validation and conditional logic: for example, show extra questions only when a box is checked.
* One entry point: share the form by link or embed it on a Confluence page, so contributors don’t use the inline or global Create buttons that skip your rules.

You get user-friendly checkboxes, and required fields still work the way you expect.

More on this: 4 Practical Ways to Collect Jira Product Discovery Ideas from Everyone

André · Answer

Thanks Christos, I was afraid this would be the case. If anyone has any other options I wouldn't mind hearing them, but yeah this is most likely it.

Christos Markoulatos -Relational- · Answer

Hi @André

You've hit two JPD limits at once, and neither has a setting to flip.

First, "unchecked" is not a value. A checkbox in Jira stores whether an option was chosen, so an unchecked box is an empty field, and empty fails "mandatory". The fields reference describes it exactly that way. No way around it with a checkbox.

Second, mandatory on the create form is all or nothing. The doc says "mark all fields as mandatory", there is no per-field option. Per-field has been "planned" since 2024, and in May this year Tanguy Crusson from the JPD team said related fixes are on the medium-term roadmap, no ticket, no date (thread). Note also that the mandatory toggle only applies to the JPD create form, ideas created inline or via the global + Create skip it entirely.

So, practical options:

* Yes/No single select, as you said. Less pretty, but it's the only field type where "No" is a real value. If you want the quick visual back in views, show it as a formula or keep the checkbox too and let automation tick it from the select.
* Keep the checkboxes, turn "all mandatory" off, and enforce the real required fields after creation: automation rule on Idea created, condition "field X is empty", action comment plus move back to an intake status, or just a notification to the creator. Catches inline and global Create too, which the form toggle doesn't.
* A workflow transition rule that blocks moving out of the intake status while a field is empty. People report it works for the transition itself but gets bypassed by drag-and-drop on the board, and I couldn't find official JPD docs for it, so test before you rely on it.

I'd do 1 for the two checkbox questions and 2 for the rest.

Hope this helps!