In Zendesk, automations can set a ticket status to Solved even if required custom fields are blank. This happens because automations check their own conditions, not the ticket field conditions. To ensure required fields are completed before an automation runs, you can use tags as a workaround. For example, you can set an automation to wait for an 'okaytoclose' tag, which is added by a trigger once the required field is filled.
For more information on managing automations, see the originalZendesk help article.
Custom ticket fields can be used as conditions and actions in Zendesk business rules. This means you can directly access and utilize these fields when setting up triggers and automations. For instance, drop-down, multi-select, and checkbox custom…
While custom fields can be added to Zendesk views, there are some limitations to be aware of. Multi-select fields, for example, are not supported in table columns. Additionally, the sort order of custom-field columns in views is determined by the…
Custom date fields in Zendesk business rules or views are always evaluated using GMT time, not the account's timezone. This means that if your account is set to a different timezone, such as GMT+2, any conditions using a custom date field will…
Yes, you can modify the tags generated by custom ticket fields in Zendesk. When you create drop-down or multi-select fields, Zendesk automatically generates tags for each field option. You can edit these tags by modifying the Tag field associated…