Timezone set and convert functions not working in automation

[Jamie Brennan]

I am working on an automation that takes a time in 24hr format (e.g., 14:00 for 2pm), entered by a user and sets the time in a date time field. The date is pulled separately and the two values are basically concatenated to generate the new date and time. 

the whole thing is working except for the timezone. Because I’m taking a text string and dropping it into a time value it’s storing the user entered time as UTC instead of America/New_York. I have been trying to apply the set time zone function to convertt it but for whatever reason it’s not seeming to work. Could anyone give me a nudge in the right direction for the syntax?

I am storing the created value in a variable using this:

{{now.plusDays(19).jiraDate}}T{{triggerissue.meeting time}}:00.000

so I have been thinking I could apply the set time zone function to the variable, 

{{meetingdatetime.setTimeZone(“America/New_York”)}}

thoughts?

[Marc -Devoteam-]

Hi @Jamie Brennan 

Welcome to the community.

Is the name of your field, meetingdatetime?

Then you need to use {{issue.meetingdatetime.setTimeZone("Australia/Sydney")}} or {{issue.meetingdatetime.convertToTimeZone("Australia/Sydney")}}

See, https://support.atlassian.com/cloud-automation/docs/jira-smart-values-date-and-time/#Set-timezone-date--- 

[Jamie Brennan]

Lord have mercy is it really because I forgot to lead with “issue”!?🤦 I will try this today when I get into the office and report back. 

[Jamie Brennan]

Hey Folks, unfortunately no this did not work. Meetingdatetime is actually a variable. So I am populating the variable Meetingdatetime at the outset of the flow with this smart value:

{{now.plusDays(19).jiraDate}}T{{triggerissue.meeting time}}:00.000

I can easily get this whole thing to work by adding "-0400" right here. But I am trying to avoid the team needing to change the flow twice a year...

I have been referencing the variable in the "create a new" action to fill a field called Meeting Date and Time using:

{{Meetingdatetime.setTimeZone("America/New_York")}} 

I also tried using the JSON entry:

{
"fields": {
"Meeting Date and Time": {
"value": "issue.Meetingdatetime.setTimeZone('America/New_York')"
}
}
}

I have been able to fill the field using the variable without the setTimeZone piece attached, it just shows the meeting as being 4 hours earlier than it is. For example if the entered time is 2pm, we enter 14:00, but after the automation runs, the Date/Time field shows 10:00. I am assuming this is because it takes the time entered by the user say 14:00, stores it as UTC14:00 and then spits it back out in the UI in Eastern, which shows 10:00.

[John Funk]

Hi Jamie - Welcome to the Atlassian Community!

So did you try it? I would think that should work but have never tried with a variable.