This has now shipped to Confluence Cloud.

jon75 - thanks, for the update.

I've not seen the the problem described. I think the best way forward is to contact support (feel free to mention my name, so I can stay in the loop), as I think we'll need to look at your instances server logs to see if there's any errors there (this is not something I can do myself).

Also, be aware that notifications are not sent if there are page or blog restrictions on the page or blog, or parent page. Having space level permissions is ok, and won't affect notifications.

Craig, I notice this was released today. Thanks for your efforts.
I have set up a space to post under all three conditions:

Blog post is created
Page is created
Page is updated

I've tested fairly thoroughly and while notifications are received for Page creates and updates, no notifications are received for blog posts to the Space home or to any Space page.

Will I open this as another bug?

Thanks

Thanks for the update – looking forward to getting this feature.

An update on the release for Cloud. Unfortunately the Cloud upgrade this week did not occur as planned (for all of Cloud, not just the upgrade for the Confluence for HipChat plugin), so we're in line for the next upgrade, being early next week.

Apologies again for the delay, and we're eager to get this release out to everyone waiting for it.

Thank you, Craig.

Hi jon75 - I've clarified the versioning, by including a plugin version number in the Fix version field. This is available via marketplace (in fact there's a new version too), that's available for Confluence Server 5.5+.

We're still in the queue for a Cloud release, and I'm expecting this to ship to customers this or next week, but there are some factors outside my control that could affect that. I'll resolve this ticket once I know that the upgrade in in production.

We are working on speeding up and smoothing out the release process for Cloud, so the situation will improve for future releases. Apologies, again, for the delay.

Thanks, Craig.
You've updated this and attached it to a version release in the middle of May.
Is that accurate?

This will be a useful feature.
You might want to tell the team responsible for pushing feature usage to stop alerts driving adoption of this feature until this is resolved. They are running today on OnDemand. That's how we found it.

This is be available in OnDemand sometime in February, and will be bundled in 5.8. For 5.7.x, a plugin upgrade will be made available via the Atlassian Marketplace or in-product via UPM.

Why was this not rectified before release? Previous integrations worked with private rooms perfectly.

Regardless, there's no reason to hide private rooms – this is a notification-only integration.

Hi Craig,

option 1 sounds reasonable, thanks.

Best,
Stefan

projekte - it's a limitation we're aware of.

We've a few options we're thinking about:

1. To link to private rooms the user needs to authenticate with HipChat (i.e. so we can get the private rooms visible to the user)
2. Provide a global option that always shows private rooms to all users (simpler)

We'd prefer option 1.

Hi Craig,

I originally posted the issue. You're right, the rooms I'm trying to link are private.
Making them public temporarily is only a workaround which will be fixed, right?

Thanks,
Stefan

amohdaris, we'll need further information:

1) Do they have any public rooms? The room search does not work with private rooms at the moment (workaround is to temporarily make the room public while linking).
2) If there are public rooms, then we will need the instance server logs. If there's an error getting the room list it should be in the logs.