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

[Armin Svoboda]

Hi, 

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.



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. 


Is it possible to fix this in my system, or is this a bug??

[Petter Gonçalves · Accepted solution]

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:

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

Let me know if this information helps.

[Armin Svoboda]

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 

[Petter Gonçalves]

You are welcome, Armin.

Have a nice week ahead. :)

[Rasmus Ersmarker]

Hi.

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...

[andrewd]

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.

[Global CMT]

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