Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Automation for Jira - Start date incorrect.

Tim van Boeschoten
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
January 24, 2022

I wonder if someone can help or is having the same issue. 

We have a set of task types which are adhoc and highly reactive. These are actioned on the day of creation or the following day. Due to the nature of these being highly repetitive tasks we have automated a majority of the fields to be populated at the task creation.

What we are finding however is that the Issue date seems to be being entered in GMT+0 where our default timezone is GMT+10 and all users are set to the default. 

Due to our location if a task is created at 9:45 am (which would be GMT+9:45) it will set the date to the previous day. However if I create a task at 10:15am (which would be GMT+10:15) the date will be todays date. Therefore I can only assume that Automation is looking at GMT and populating accordingly. 

It seems others may have had this issue. We are on Jira Cloud so I don't know if this makes a difference. 

2 answers

1 vote
Pramodh M
Community Champion
January 24, 2022

Hi @Tim van Boeschoten 

Automation for Jira is nothing doing wrong here, everywhere in your rule change the actor to the profile who has set the GMT time to your location, and you should be good!!

Let me know if this works!!

Thanks,
Pramodh

Tim van Boeschoten
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
January 24, 2022

Thanks for the response. So it seems that Automation for Jira acts on GMT only would that be correct? I will find an appropriate user to trigger, thanks :)

Like John Funk likes this
0 votes
John Funk
Community Champion
September 1, 2022

Hi @Tim van Boeschoten  - Did Pramodh's response answer your question? 

Tim van Boeschoten September 1, 2022

From memory. I had to add +10 into the timer. Daylight savings come into consideration however that won't be a problem until the operations and services of that team move to 24/7.

Suggest an answer

Log in or Sign up to answer