Ticket custom field mandatory when is empty | The place for Zendesk users to come together and share
Skip to main content
Feedback submitted

Ticket custom field mandatory when is empty

Related products:Support
  • March 26, 2021
  • 4 replies
  • 4 views

I have the "type of issue > motive" ticket field configured in my zendesk workspace and it's mandatory only when an agent changes the status of a ticket to solved or submit it as solved, but we need it mandatory even if the agent submit the ticket as pending, on hold and solved. I configured a trigger but it only notifies the assignee agent by email and allows to submit the ticket as pending , onhold ...

4 replies

  • March 29, 2021

Hi 1261998837109 - Does your plan include Conditional Ticket Fields by chance?

If so, you could add this ticket field as a condition and then make it required when the status is Pending, On-Hold or Solved. You'll just want to select a ticket field that is always present on your tickets & then add multiple rules so that this conditional logic always validates to true

For instance, as long as the Priority field is always set for tickets in your Zendesk instance, you could have a conditional logic rule that looks similar to the below:

You would then build 3 identical conditional logic rules for the other Priority levels: Low, High and Urgent. 


Sydney12
  • June 1, 2021

We need mandatory fields on all Status's, not just solved. This conditional field workaround is not able to work for our team as there are many fields we use that need to be mandatory. Is there anything on the roadmap for including this functionality?

Thanks


Dave12
  • Employee
  • June 2, 2021

Hi Sydney -

Zendesk's free Ticket Field Manager app will allow you to specify fields that are required in order to submit a change on a ticket, and much more: Installing and using the Ticket Field Manager app. Does that seem like it could work for your needs?


Sydney12
  • June 9, 2021

@Dave Dyson

 

Thanks for that app! It looks like it could work. I do have some questions as it was not documented in that article:

  • When testing, we noticed that when a field is already mandatory on Solve and it is mandatory in the app, it will add 2 asterisks. Is this intended?
  • Every ticket that has a mandatory field enabled in the app requires the field to be filled in before any status is updated (New, Pending, Open, etc). Is there a way to adjust this so that the fields are mandatory on Pending and not on all status updates?