Timezone difference after migrating Jira to new location.

Vijay Sv
Contributor
July 23, 2019

Hi All,

 

We recently migrating our Jira server from Pacific Timezone to Eastern Timezone, during migration we have set the new server timezone to pacific(Referred KB: https://confluence.atlassian.com/adminjiraserver072/migrating-jira-applications-to-another-server-828787651.html) and later we switched the new server timezone to Eastern. Now the timezone change from PST to EST caused the times to be 3 hours behind for all the issues which in turn affecting our SLAs.

Can anybody suggest a way to fix this issue? unfortunately above KB doesn't give any information on post-migration timezone setting :(

 

Thanks,
Vijay 

1 answer

1 accepted

1 vote
Answer accepted
Petter Gonçalves
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
July 24, 2019

Hello Vijay,

I understood that you have set the default timezone of your new instance to Eastern after the migration, however, this change also affected your SLA, causing your issues to be 3 hours behind the actual Eastern Time. Is it correct?

As long as I verified, SLA calendars are not related to the Timezone configures for your instance, although it receives the default value once it is configured. That being said, I would recommend you to check the calendars configured for your Service Project:

- Navigate to your SD project > Project Settings > SLAs > Calendars

- Change the timezone of your Calendars to be configured with the correct Eastern Time

Screen Shot 2019-07-24 at 14.09.58.png

Also, double-check if your personal timezone is properly configured with the Eastern time:

1 - Click in your Profile Picture at the left-bottom corner > Personal Settings

2 - Check if Your Timezone is properly configured

Let me know if the steps above work for you.

Vijay Sv
Contributor
July 24, 2019

Hi Petter,

Thanks for the suggestion, perhaps we are using Jira software and Time to SLA plugin to calculate SLAs. I Could able to figure the solution when we move the Jira server from one location to another(PST to EST) to avoid Datetime differences and in our case, it was 3 hours gap.

 Well, here is what we did.

  1. JVM and DB on PST => Initial times. (JVM was using Jira server default pacific time zone since we didn't add any timezone parameter in the JVM)
  2. JVM and DB on EST => After migrating Times shift 3 hours backward.(JVM was using Jira server default eastern time zone since we didn't add any timezone parameter in the JVM) 
  3. JVM on PST => Times shift 3 hours forward.(Now we added "-Duser.timezone=America/Los_Angeles" in the JVM parameters to continue to use pacific at the application level irrespective of Jira APP and DB server's timezone).

And, that resolved our time travel issues:)

 

Regards,

Vj

Like Petter Gonçalves likes this
Petter Gonçalves
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
July 25, 2019

Thank you for sharing the steps you took to solve your issue, Vijay.

Have a nice day! :)

Like Vijay Sv likes this

Suggest an answer

Log in or Sign up to answer