Recent searches
No recent searches
Trigger condition with evaluation of the numeric value in ticket field
Answered
Posted Feb 14, 2022
In this moment the trigger condition based on numeric ticket field can only perform two basic stance: "Present" or "Not present".
It's quite icredible that there is no way to have a trigger condition base on the value of the numeric field like: "is more/less than" -> "1000" etc.
Anybody has a workaround to solve the trigger condition with numeric value in the ticket field?
16
16
16 comments
Diogo Maciel
Specific examples, details about impact, and how you currently handle things are helpful for our product teams to understand the full scope of the need when working on solutions. You may also want to review the Product feedback guidelines and how to write an effective feedback post [https://support.zendesk.com/hc/en-us/community/posts/4404146647066-Product-Feedback-Post-Template].
We truly value customer feedback and your voice and votes in the forums help influence future Zendesk functionality.
1
Riccardo Centomo
Hi @...
The link to write an effective feedback post seems doesn't work..
Specific example is here: https://support.zendesk.com/hc/en-us/articles/4408832737818-Workflow-recipe-Creating-an-approval-process
Wen we need to manage an approval workflow process we have to manage many time treshold for the value in specific ticket fields, like "if ticket value is more than this.. trigger have to change the assignment group ticket and scale to Manager..".
In other process we need to perform calculation between value in different ticket fields to manage the trigger action, because the total value of the ticket is more than.. And the trigger has to assign it to the Manager approval..
1
Diogo Maciel
Thank you for your contribution! Our community is always reviewing feature request feedback and suggesting these changes to our product managers. You can follow our updates in our Release notes below
https://support.zendesk.com/hc/en-us/sections/4405298847002
1
Lawrence Dye
This would be an extremely useful feature for me as well.
We currently have a short form containing text fields that users fill out and submit. I would like to be able to create a trigger based on the input of that field, but as mentioned above, the only current option is "Present" or "Not Present", which is not helpful for this use case.
3
CJ Johnson
It looks like you also cannot set a numeric field via a trigger. This is a major limiter to how useful this field can be. I'm going to have to go back to the drawing board for a project because of this. I'm trying prioritize based on the values in 3 separate fields, only 1 that is always present. I thought a matrix in the style of r-w-x would work well and make sense, but the system's not allowed to set a value for those fields.
1
Alex C
+1 About having more condition options using the Number field. I would have imagined that the main use case and selling point of this field would be the "less than/more than" conditions you could apply on it.
2
Lloyd Norman
Hey team,
Would be really valuable to have something like this.
We've come across a few examples where this would be very useful.
1
Rick Marx
Another vote for this, this would greatly help us automate certain cases.
We would appreciate the option for Is Greater Than / Is Less Than / Equals as well.
Our use case: We filter out certain tickets based on a number field, either these numbers are deprecated in a way, or numbers below a certain point should go to a different group for example.
1
Dan R.
Just got bit by both this issue and the fact that automations don't support numeric fields either. It would be super if we could be allowed to evaluate and act on data in our systems via the Triggers and Automations features.
All data that goes in a field should be able to be evaluated and be acted on.
2
ASPOCK Admin
+1, this would really help us automate certain cases.
e.g: If the one of the ticket field (custom) value is 5001, I am should be to categorize the ticket automatically as >5000 category using a trigger.
0
donna henry
Currently have to manually review and act on numeric fields for workflow processing...i.e. procurement request...does request require secondary approval based on $ threshold? Would be very helpful to have a trigger automatically forward for approval prior to landing in procurement dashboard...
1
Vitalii Petrus
+1
0
Rafa D.
I have a solution for this situation, you can read the field value via Liquid markup in a webhook.
In my case, I want to create a new priority field with more options and starting with a number, in order to sort tickets with it.
I also want to change the priority based on the value of another custom field.
I created a webhook to the endpoint ‘https://orenes.zendesk.com/api/v2/tickets/{{ticket.id}}’ and used it in a trigger with the following JSON:
Here ‘ 19356697887122’ is the priority field and ‘20703424763538’ the numeric field.
The line ‘{% assign field_value = ticket.ticket_field_20703424763538 | times: 1 %}’ multiplies the field value by 1 to convert from string to number.
The Liquid markup then checks the value and returns the corresponding field tag.
You will need to adapt the code for each case. For changing the group, the code should look like this:
(Note: I haven't tested this last code snippet.)
1
Jessica C.
+1 on having a way to do this via the triggers UI
We have partners who sometimes work with multiple customers at a time. So they may be submitting support tickets from the same email but for different customers. We collect the customer ID in our support form and our use case would be to have the ability to associate specific partners to specific Zendesk orgs by the customer ID and not by their email domain. However the current trigger UI only allows you to specify whether or not that numeric field is there.
2
Hannah Ehrlich
+1ing to add this. Really need to be able to base on a > or < number in one of my fields.
1
Joel Cohen
This is a great feature request and I have added it to the backlog for future consideration. This means that we will think about adding it as a priority later in our planning cycle. We are going to leave this post open for comment to allow others to provide their feedback and use cases, however please note as is stated in our Community Guidelines that we can not commit to prioritizing any one piece of feedback we receive in the community.
Thank you again for your feedback and for being a valuable customer with Zendesk.
0