Promoting product updates/releases on Company Hub?

[chris sieverts]

In an effort to communicate what is in a release track to our Confluence users, is it possible to post the list changes in a Company Hub widget or some other way? In a perfect world we could choose not to include some changes that are more backend/administrative.

Thanks!

[Gunjan Jeena]

The most elegant solution, I believe, is to set up an independent "Product Updates" or "What’s New" page within Confluence which you can promote using Company Hub. You can choose only those product changes from Atlassian that will be really interesting for your users, instead of publishing all the technical details of their backend changes.

If you use release tracks, you can also track the release notes on the official Atlassian cloud site and then provide a summary of interesting updates to your internal page. In addition, providing a brief explanation of why this particular update happened may be more helpful than just publishing release notes.

[Tomislav Tobijas]

Hi @chris sieverts ,

I guess you could use Jira Issues macro for that and simply filter out all issues/items you'd like to display. Although, in our case, we do create a release notes page where apart from using the mentioned macro, we have a more detailed explanation for released features, separated by headings/sections. If you'd use this approach, then I guess you could simply link this release page to the Company Hub.

This kinda depends if Confluence users also have Jira license or not, but even if not, this path with a release notes page would probably be sufficient.

Feel free to share some additional details (if you have them) to maybe see if there's another potential solution.

Cheers,
Tobi

[chris sieverts]

Thank you @Tomislav Tobijas however I have realized that I didn't include in my original post that I was referring to Atlassian's product updates. I would like a way to share the updates to Jira & Confluence that they are rolling out to the cloud with our users so that they are aware. 

[Tomislav Tobijas]

Ah yes... @chris sieverts I can just say we're kinda struggling with this as well. I still didn't find some decent solution on how to properly communicate the changes apart from documenting those manually (e.g. Atlassian admin or someone to create a page or blog post about the changes).

It also depends if you're using release tracks or not, and you can probably make some subscription or RSS feed based on official cloud release notes or cloud roadmap, but again, we haven't made a clear way of announcing all of these changes just yet ☹️