Match custom object nesting parity with ticket custom fields

I use Zendesk custom objects to clone SFDC custom objects. In SFDC, two objects have a hierarchy. I would like to replicate the same hierarchy with Zendesk custom objects and condition fields; however, custom objects don't follow the same nesting logic as custom ticket fields i.e. custom field A::custom option 1.

Just as Zendesk understood that custom ticket field options should be nested, your admins using custom objects have realized so should be custom objects. Ticket fields still have the lookup, so nothing about linking the ticket field to the custom object via lookup should impact.