When a ticket is created we pass in a Standards of Care value via a hidden field. This triggers an automation rule to modify a date field. For example, add 8 hours, which adjusts the date field forward one day given it is only utilizing business hours. This works via `{{issue.created.plusBusinessHours(8)}}`
We are attempting to now utilize a custom date time picker field so we can be more specific with the due date and time. Using the same smart value above sets the date correctly, but does not modify the time, which stays stuck at 1:00PM regardless of when the ticket is created.
I've tried a few modifications to the above smart value, but that only end up breaking the automation completely.
How can we go about modifying the date time picker field with the correct date/time values?
Thank you in advance!
@Josh Bray welcome to the community!
Are you sure it is a date and time field? not a date field?
What happens if you use {{issue.created.plusBusinessDays(1)}} instead?
Can you share a screenshot from your automation rule and audit log as well?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.