Thanks all for your feedback and apologies for the delayed response. This issue has now been resolved for all Cloud customers with the maintenance performed on Monday 18 jan. If you are still experiencing problems, please raise a support ticket so we can investigate further.

Cheers,

Vincent Kok
Atlassian

Yes, I am aware of the issue linking. However we all know in JIRA that statuses are usually paired with resolutions. The resolution is duplicate.

Steven, that issue is very super clearly not marked as Duplicate here. It only mentions there was an identical issue that has been resolved.

Just so you know.

Best regards,

Xavier

Xavier, that issue is very very clearly marked Resolved as Duplicate.

I'd encourage others to bump up the severity on your support issues! They are there to deal with these issues.

Same for us, it is still an open and important issue.
We did not receive any information about how to restart the site yet. Are there any updates to this issue?

Atlassian!
You are really playing with customer patient. This post is not just about this issue.

Please, could somebody responsible answer me and your customers how it is possible to give "GO" to roll out MAINTANANCE release with such a mess?? This is not for a first time. We struggle every week with some issues which were caused by a new release (back up not working, fields are missing, ....). You are giving others tutorials for Agile development, Continuous integration and what about Quality, customer satisfaction with a new release?

Thanks for your answer!

I see this bug is cloned as CONF-40450, which is marked as resolved (and was labeled Major priority)

For us however it's not resolved yet. Macro's are rendered as " Broken macro" now.

Any updates? Can we restart the site by ourselves? (We've had no response from support regarding our question to restart the site)

I noticed this bug affecting a bunch of stuff in our confluence this morning. Support was able to apply a workaround for me that got things back to a functional state. Thanks support!

In short, Connor, you don't. They [Atlassian] have to restart cloud instances.

Hello again cmccarty! You'd have to ask http://support.atlassian.com's support to perform administrative actions on your part, they can usually help you quickly if this is impacting your business. They may be able to fix the issue without restarting, I'm not certain of a root-cause on this issue yet so I'm not sure what route they'd take to solve this for you.