Hi All,

The fix has been rolled out to all Atlassian OnDemand instances, if you're still seeing this error in Atlassian OnDemand please contact Atlassian support at https://support.atlassian.com.

Regards,
Matt

Hi All,

As nmason mentioned, the fix will be coming on at the start of next week. However, if you'd like it to be implemented immediately, please log a ticket with support.

We still do not see the fix deployed to our instance (primosoftware.atlassian.net). When will this be deployed?

Hi,
I'd just like to add that we too have moved a 30-man project to using an OnDemand confluence instance instead of e-mail for project announcements. This blog macro was our primary tool for doing this. In other words: it's important that it 'just works'.
It is especially disappointing that it was announced that it would be fixed on Wednesday when I now have to wait an additional 5 days for the fix to appear. It would have been great if the information in Nick Mason's post (25/04 20:31) would have been available on Wednesday.

Hi all,

The fix will be coming in the regular maintenance window at the start of next week (Sunday/Monday night, depending on your timezone). If you'd like us to apply it before then, please raise an issue in the OnDemand Support project at support.atlassian.com. Be aware that it'll require a restart of your applications, there'll be around ten minutes of downtime so let us know when your preferred window for that is.

Sorry Adam,
You should have received the fix on Wednesday, which is still too slow, we've encountered an issue deploying fixes which delayed getting this fix out until Wednesday. The release of this bug has also highlighted a flaw in our release process, it shouldn't have made it into production. We're working to fix this process.

I'm talking with support to ensure a senior support engineer is looking at your specific support case to see why this is still occurring on your instance. I apologise that it has taken so long to fix your problem.

Steve

Hey guys,

We use the blog macro as core functionality and I moved an entire department off Gmail to Confluence, only for this to happen after one month and now I have had to backtrack and tell them to go back to checking their emails!

I told them a fix would be deployed yesterday based on your feedback, and it still hasn't been resolved?
What is going on?

Steve,
Some constructive feedback for you: You really need to review how this error has been handled, because I find the entire episode extremely disappointing. Here is why:
(1) I do not know if this is affecting all clients, or only the ones commenting here. If it is all (or a large percentage) of them, I don't accept the excuse that it is impossible to test everything - Macro's are CORE FUNCTIONALITY.
(2) I logged a ticket, but haven't received any updates since your first response two days ago. The ticket has been changed to a status of 'Waiting for Customer'. Waiting for what exactly? I am fairly sure I am waiting for YOU to fix the issue!
(3) Until your comment on this board from 24 April (yesterday) about 'working to get this fix deployed today', no ETA has been provided.
(4) The time frame you provided yesterday was misleading and you have not provided any update. The macro is still broken on our instance.
(5) I still therefore have absolutely have no idea when this issue will be resolved, no advice on what to do in the interim, and I am left with a feeling that going to On Demand was a huge mistake.
Very disappointed.

I would assume when such a global issue occurs and it been fixed that this will be updated on all instances right? So I don't see any reason to open a new ticket with more or less the same information in this ticket here for example. Do we need to do anything in addition to that or will the blog section simply show up correctly again?

Hi Andreas,
We are working to get this fix deployed today, please raise a support ticket to receive specific updates as to when the fix has been deployed to your instance.