Ticket object model is more robust when looking up a field value. This is useful when requesting a value for a custom field on a ticket that has been created ''before'' that custom field has been added. Related to #5099, but this has use-cases besides the templates, that's why the fix has not been done at the template level.