Date Time set on custom field using Automation

Jose Ocando May 19, 2020

The issue lies in the function that sets the time and date based on today's date for a specific field inside of the automation.  For instance, if  we specify the following in the field:

{{now.withHour(16)}}  -   // It should set the time at 4 pm, it is currently setting it up at 2 am 

We can do some work around this by setting it up to a number that matches the hour difference, but it will not be technically correct or a responsible setup. We have also checked the time zones in our Jira instance, and it is appropriately set up to Sydney/Australia.

We have also tried the following, in an attempt to adjust the time difference

{{now.toDateTimeAtStartOfDay("America/Los_Angeles").withHour(16)}}

With no success, Any thoughts?

1 answer

0 votes
joehardin
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
November 12, 2020

Jose,

 

I have noticed the same. Automation seems to be based on a single, central timezone (UTC I think). I'd assume this wont be fixed anytime soon and that changing your automation parameters to account for the differential would be a long term solution. 

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Site Admin
TAGS
AUG Leaders

Atlassian Community Events