local time does not match between Jira Service Desk and Jira Assistant

[ITGuyOhio]

When I record time in Jira Service Desk (ex 15min logged at 07:00 AM) the incorrect time is displayed in Jira Assistant (from previous example 15min is logged at 05:00 PM not 07:00 AM). I've checked the Time Zone setting matches in the Jira Assistant-User Groups and in my Atlassian profile chrome-extension:///index.html#/2/settings/usergroups https://id.atlassian.com/manage-profile/account-preferences What else am I missing? Please advise

Thanks Matt Kinne

[shridhar-tl]

Hi @ITGuyOhio , You will need to verify if your local timezone is same as that of Jira's timezone. The timezone you set in User groups is just for viewing the report. But when you log the work, it would log based on your local timezone.

[ITGuyOhio]

Thank you for the response. I will confirm this. I actually think it is an issue with Google Chrome (other browsers report the correct time). If I visit http://browserspy.dk/date.php or https://whatismytimezone.com/ They both report my time is 10 hours ahead.

again, thanks for the response. If you have any thoughts on my last comment I'd appreciate some ideas.

I've already tried many things Confirmed BIOS time Confirmed system time/timezone wiped and reinstalled Chrome logged in with fresh user account

Matt Kinne

On Fri, Jan 22, 2021 at 9:47 AM Shridhar TL [email protected] wrote:

Hi @ITGuyOhio https://github.com/ITGuyOhio , You will need to verify if your local timezone is same as that of Jira's timezone. The timezone you set in User groups is just for viewing the report. But when you log the work, it would log based on your local timezone.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/shridhar-tl/jira-assistant/issues/182#issuecomment-765118497, or unsubscribe https://github.com/notifications/unsubscribe-auth/AORGXYL6HLKAIL7EWAFY77TS3D7NHANCNFSM4WLBOXXQ .

[shridhar-tl]

@ITGuyOhio - As it has been too long and there are no activity or similar reports from any other users, I believe this issue has been resolved. Hence closing this issue. If there are still similar issues faced by any uses, please feel free to reopen this ticket.