Question
When I use a custom date field as a trigger condition, what do Is within the previous and Is within the next do?
Answer
Is within the previous and Is within the next evaluate conditions based on an integer number of days. Each day is translated into 24-hour multiples on the backend.
For example, Custom date field | Is within the next | 3 means the condition will evaluate as true when the timestamp of the custom date field is within the next 72 hours.
The timestamps for date fields are a more complicated issue since they’re not exposed anywhere in the UI or the API. In general, the hidden timestamp related to a custom date uses 00:00 to 23:59. When a trigger uses the condition Is within next | 1 day, the trigger would be expected to run at 00:01 onwards.
For more information about creating triggers, see the article: Trigger conditions and actions reference.
28 comments
Mattia Tosti
Hi Clifford!
We have a custom date field associated to our users called <published_at> that indicates when the user published a listing on our marketplace. We have a trigger that does the following:
We use the tag to group all tickets that need onboarding in a view. We need to create a trigger that removes that tag if the listing is older than 3 days.
0
Clifford James Lacson
Hello Mattia,
May I know what exactly are you trying to achieve with the opposite of "is NOT within the previous" or "is NOT within the next"?
You may check out some of the Trigger actions and conditions here for more guidance about it: Trigger conditions and actions reference
Clifford James Lacson |Customer Advocate
NEW - Zendesk offers free, on-demand training for all of our products. Set up your account and start learning today at training.zendesk.com
0
Mattia Tosti
Hi! How can I have a trigger running for the opposite: "is NOT within the previous" or "is NOT within the next"?
2
Bart
Hi All,
Need a hand with the custom date setting.
We have new businesses that sign up, and I'd like for a trigger to only fire once for their very first ticket and take into account the custom date. For example, if a business signed up a week ago, but has never written to us, and this is their first time, I want to add a tag, so I can add it to a view and add an internal comment on steps / processes for agents. If the trigger has fired before - and the business writes again, we don't want to have that trigger fire again. What's the best solution around this?
Thanks
0
John Brunker
Just like Peter mentioned above, we are looking for the exact same solution....
All I want is my custom date field to activate an automation saying "Follow-up date has arrived" and send out an email.
Has anyone found a reliable way to implement this? Any help would be greatly appreciated.
2
Francois Spinnael
We are trying to do the same with a "follow-up-date"
Basically a date that the agent defines when he has to re-check that specific case.
The solution with the tags only works onces per case.
If the agent put a new "follow-up-date" well it will not run the automation anymore because the tag has been removed...
I was thinking to clean "The follow-up-date" but this isn't something that zendesk can handle...
Any solution by someone?
>> Maybe found a solution: I put the date on 1990-09-01 and adapted the trigger to not give a tag if that date is present
0
Dave Dyson
25328965947 That does sound frustrating, I'm sorry to hear it. I wonder if this (paid) app might be of use?
Deadline
0
Jeremy Holmes
We wanted to move away from requiring every single ticket to be a task since it is the only way Due Dates work. Unfortunately, the custom date option doesn't work either because there is still no way to trigger to open on the day that it is due. We created a complex workaround, but now have an issue with everything being based on GMT so it is still causing issues because things are opening the night before. We are now scrapping the whole concept and going back to making every single ticket a task. We would love if we can have a custom field that either works like Due Dates or just expand on the functionality of Due Dates and stop limiting them to only Tasks. We would prefer to be able to tie individual problems to incidences and still have the tickets function the way we need. Zendesk is severely limiting it's users by not doing something that has been requested since before I started using the product. I have come across multiple discussions and found references to parts of the support site that have been cleared out. It would also help foster a sense of real community if coming across questions posted that are listed as answered had answers that were serious considerations of user needs and not just a blatant disregard of the user needs. Also, since I'm on about it, a time option would be great too. Most of our users are working only out of Zendesk and even if they do have Outlook, don't want to set up a calendar event to work a ticket.
6
Sign in to leave a comment.