Boolean Value Custom Fields

It would be great if we could have some boolean value custom fields. For me personally it would be extremely valuable to our API integrations.

For example, i’d like to have a custom field that is called ‘blocked’ which is just a true/false or a checkbox.

Obviously a similar thing could be achieved with a ‘status’ field i.e. open, in progress, blocked or it could be achieved with a ‘blocked’ tag. But the UX would be far cleaner if I could just tick a box.

I can see plenty of great applications for such a field and would tie in nicely to automations on those fields.

This is possible today.

1 Like

Yes, you can do that, but when you interact via the API it’s not a boolean value, you have to go through the custom fields and interrogate the values for string ‘true’ or string ‘false’ it’s not clean.

Hi @Frank_Clark, thanks for taking the time to provide this feedback!

While this type of custom field isn’t available at this time, hopefully it’s something our Product team can implement in the future .

I’ll keep you posted and let you know if we have any updates :slight_smile:


While it doesn’t solve your problem, the best workaround for now, I feel, is a single-select custom field but with one option value, not two. So your Blocked? custom field would be defaulted with no value and you have the opportunity to value it with a checkmark :heavy_check_mark: when true. Of course, in the API it’s still not really a Boolean but in the UI it actually operates nicely to avoid distracting until it’s turned on.


1 Like