Using custom ticket fields in business rules and views Follow

all plans

When you add custom ticket fields, you can use them in triggers, automations, and views.

For information about adding custom ticket fields, see Adding custom fields to your tickets and submit a request form.

Understanding custom ticket fields, tags, and business rules

The drop-down list and checkbox custom ticket fields can add tags to tickets that can be used in your business rules.

With drop-down fields, Zendesk Support automatically generates tags as you enter field options for your custom field. You can modify the automatically generated tags by editing the Tag field. You must have a tag for each field option.

With checkbox fields, you have the option of associating a tag with the field.

These tags can be used as needed in your business rules. For example, you might use the tag to automatically assign the ticket to a specific support group. For an example of how to use tags in business rules, see Using tags in macros, triggers, and automations. For more information on the relationship between tags and ticket fields see, Understanding tags and ticket fields.

The custom fields are also available as conditions and actions in business rules, which means that you can directly access the custom fields in your business rules rather than having to access them using the Tags action or condition.

Understanding custom ticket fields and views

After creating a custom ticket field, you can add it to your views. For example, suppose you create a custom field to let users select one of your product lines. After adding the custom field as a column in a view, you can sort the tickets by product line by clicking the column's heading. For more information on views, see Using views to manage ticket workflow in the Agent Guide. To add fields to your views, see Setting formatting options in the article.

The sort order of custom-field columns in views is by the underlying tags used for the custom field. For example, if you sort the tickets by ascending order, the order is by the alphabetical order of the field's tags, not its titles.

For example, suppose you create a custom drop-down menu with the following product lines:

  • Photography (tag: photography)
  • Video (tag: audiovisual)
  • Medical (tag: endoscopy)

If you add the field to a view and sort by ascending order, the tickets would be grouped and ordered as follows:

  1. Video tickets (tag: audiovisual)
  2. Medical tickets (tag: endoscopy)
  3. Photography tickets (tag: photography)

If you want to list your photography tickets at the top of the view, click the column heading again to sort by descending order.

About required fields and automations

If you have automations that set the ticket status to Solved, the ticket will be set as solved even if the ticket has "required" custom fields that are still blank. The reason is that automations check the automation conditions, not the ticket field conditions.

A workaround is to use tags to prevent the automation from running until the required fields are completed. For example, you can tell the automation to hold off until the okay_to_close tag is present, then set a trigger to add the tag when the required field is no longer blank. Here's how. Add the following "All" condition to your automation: Ticket: Tags > Contains At Least One of the Following > okay_to_close. Next, create a trigger with the following "All" condition: Ticket:{custom_field_name} > Is Not > - (blank). Set its action as Ticket: Add Tags > okay_to_close.

For more information, see the following articles:

Have more questions? Submit a request

Please sign in to leave a comment.

Powered by Zendesk