Hi everyone,
I have a rule to set a date on a custom field by ai studio. That part works correctly, but I cannot get AI studio to set the time to pacific. It keeps entering time as UTC, even when I explicitly say to convert to pacific in my rule. Any thoughts here?
Hi @Arthur_BEGOU ,
Thanks for the answer. Just tried both options and they didn’t work, unfortunately.
Hi Sako_Kassabian,
I can understand the frustration there. Time zones can be slippery, especially when AI is in the mix
Just to clarify: Is your profile time zone set correctly in Asana? Profile Settings → Display → Time zone
I would suggest setting the task’s Due date/time instead of a custom date field
I’ve had better luck with rules + AI Studio respecting local time when targeting the task’s due date/time. If you need to keep a custom field for reporting, you can mirror the due time into it afterward with a separate rule.
Hi @Liz_Carpio
Thanks for your support here.
I’ll let @Sako_Kassabian confirm his issue; but I feel your comment doesn’t answer completely his question.
Did you manage to get AI choosing a specific timezone and implement it in a date field?
For example, with multiple fields displaying different times?
As a prototype showing this capability, we could imagine a project dedicated to display the World timezones in 43 fields.. (just an example for you to understand where I’m going with this
)
Hi @Liz_Carpio
I actually don’t see a time zone option in my settings and I’m a super admin on my tenant.
Also, my use case is to track the time difference between create date and our custom field that tracks first response date/time. Our create and due dates are in local time zone, but asana ai isn’t respecting those rules. This data is going to our data warehouse, so I can just change it in there, but in Asana it looks weird.
Hi Sako, will you be able to provide a screenshot of the prompt you get? Sometimes it’s in the order of steps in the prompt that needs auditing