Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal


  • Give kudos
  • Received
  • Given


  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

HELP: Time zone issue? Start date / end field time zone doesn't match JIRA time zone Edited


Having some weird time zone issues in JIRA.

I'm using next gen boards and have some automation set up using the standard 'update an issue field' feature in next gen. 

I have a rule set up to enter the current date and time when an issue is moved to 'Done'. See screenshot below.

Screen Shot 2019-07-02 at 3.42.46 PM.png

However, when this rule runs it has a 12-hour discrepancy with the time in the ticket History? See screenshot below displaying the time discrepancy. 

Screen Shot 2019-07-02 at 3.33.15 PM.png
Is it possible to fix this in my system, or is this a bug??

3 answers

1 accepted

0 votes
Answer accepted

Hello Armin,

Thank you for reporting this problem.

In fact, I was also able to reproduce the same problem in my Cloud instance and confirmed it is a bug in JIRA Application.

The timezone selected in the background of the next-gen rules is in GMT, not respecting the current timezone of your instance.

I have reported the following bug report with our development team:

Update custom field rule of Next-gen add the wrong date/time for Time Stamp field

Feel free to vote and watch the bug to receive notifications about its fix implementation and possible workarounds.

For now, the only option I found to work around this problem would be to use Automation for JIRA Lite App, configuring a rule to perform the same action:

Screen Shot 2019-07-10 at 18.19.25.png

P.S: The mentioned plugin has 300 free executions per month.

Let me know if this information helps.

Great thank you. I'm using this plugin now. However, when exporting issues to excel, it still exports in GMT. But that's no problem, I can write some a code to change it. Thanks for your help @Petter Gonçalves 

You are welcome, Armin.

Have a nice week ahead. :)


Any update on this 1 year later? 

I have the same issue when trying to set set the start and end date field from my plugin.


I don't understand how you set the severity level of a bug.

How can it be a "minor" bug that you show the wrong start/end date in a project-management tool? That should be feature A1...

This issue appears to also affect Classic projects in the Cloud space. It is not limited to just Next-Gen style projects.

I tested this in my own Cloud instance. It appears that the date/time values are given the offset that relates to the timezone set in your User account settings. As I am in Brisbane, Australia, my timezone is GMT+10. Therefore, when I set a date-time field, Jira will offset the time by +10 hours. The same occurs if I change to other timezones - GMT +4 will add 4 more hours to my date/time value/s. If I change my user account timezone to GMT 0 (e.g. Africa/Abidjan), any values I apply to my date/time values remain unchanged.

0 votes

@Armin Svoboda Is it okay to share the "workaround" for this issue? 

Suggest an answer

Log in or Sign up to answer

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you