Profile time zone won't change after 12 days of it "taking a while for changes to take effect"

[Heather Blue]

We are trying to use shared calendars in our company Confluence spaces but we are having issues getting the events to display for employees correctly, seemingly because their profiles aren't changing time zones when they change them.

One employee changed the settings 12 days ago and still gets the message below when trying to change it again.

Any ideas why this is happening or why it is taking so long for the profiles to reflect the time zones employees are changing their profiles to?

[Fabian Lim]

Hi @Heather Blue

I recommend you open up a ticket with Atlassian support to see if they can assist you faster.

Regards

[Heather Blue]

Thanks Fabian. I'm going to ask my company admins to submit the ticket. It does seem like a bug, I don't think it should take 3+ weeks for the change to take effect.

[Guy Anela]

Hi @Heather Blue - Did you or your admins ever get anywhere with this? We're exhibiting the same issue. :( 

[Heather Blue]

@Guy Anela our IT department submitted a ticket 4 days ago but we haven't heard back from Atlassian yet. We do believe it is a bug though, based on some more testing we did. I'll update this post and tag you whenever I hear back about it!

[Guy Anela]

Thanks @Heather Blue!

I agree, it's definitely a bug. I opened a Support ticket as well and they pointed me to CONFCLOUD-72744. Based on the below Comment, doesn't sound like they'll be addressing it anytime soon. :( 

Puneet Jain added a comment - 29/Sep/2021 2:53 PM
Hi All,

The issue occurs only for few hours as it takes time for timezone to be updated across all edges servers and downstream systems. The above is conveyed to users via pop up which is displayed when timezone changed in identity.

The issue is a legacy issue and has been present since beginning. The same has not been introduced recently.

The long term fix would require change in the current architecture and hence need more time.

[Heather Blue]

Thanks for passing this along @Guy Anela hopefully Atlassian can prioritize this, because the calendars aren't usable across time zones so long as this issue persists.