How is everyone managing non-GA release notes in your Community, and how do you separate those from the feature releases you want to highlight?
We’re looking for a place to house things like bug fixes, minor improvements, and small UI/UX changes, updates that are important for customers to know but aren’t necessarily something Product Marketing would formally announce.
Today, we share our roadmap through a Productboard iframe, but I’m curious if anyone is doing something similar for non-GA updates using Jira or another tool.
I’d love to hear how others are approaching this, open to any ideas beyond using the standard product updates functionality.
Best answer by mbuuck1
Hey Ryanne! This is a good question. We don’t have a perfect solution, but the following two practices have mostly met our needs here:
when we’re made aware of one of these types of updates, doing a mini audit to find all related conversations and make sure that those posts reflect the new change, whether that’s formally updating the status on a requested feature in the Ideas module or simply adding an update comment to an existing thread.
We do a quarterly roundup of these exact things and just post them in our main community. You can see an example here! Obviously these aren’t housed separately or designated as anything super formal like Product Updates are, but we’ve found the specificity and searchability of the updates generally get the job done, at least when our users are actively asking questions/looking for information on that topic (whether in the community directly or increasingly, via AI.)
Hey Ryanne! This is a good question. We don’t have a perfect solution, but the following two practices have mostly met our needs here:
when we’re made aware of one of these types of updates, doing a mini audit to find all related conversations and make sure that those posts reflect the new change, whether that’s formally updating the status on a requested feature in the Ideas module or simply adding an update comment to an existing thread.
We do a quarterly roundup of these exact things and just post them in our main community. You can see an example here! Obviously these aren’t housed separately or designated as anything super formal like Product Updates are, but we’ve found the specificity and searchability of the updates generally get the job done, at least when our users are actively asking questions/looking for information on that topic (whether in the community directly or increasingly, via AI.)
@ryanne.perry I dont have a fixed answer for you but here is what we do:
On our community we use the product updates to communicate about larger product updates and also show more and offer customers the option to have a conversations amongst them about new releases and where necessary a product manager will join in
We have an integration with product board which forwards product feedback given on the Community into Product Board. And to make is easier for people to also reach product board an give product feedback we embedded our roadmap in Product Board into our Community via a iFrame.We also use productboard updates/notification when we released something and all people who responsed to a topic will get an email notification that there is an update and it's visible on the product board card
We also hae our own releasenotes page where we also communicate all releases.. big and minor. It is not integrated on our community platform yet. But we want to make is available in there as well in the near future
We also have our own internal support tool via which we communicate about bugfixes and that is easily accessible (link) in the Community as well so that people can easily read up on it.
But if you want to move everything to your community, I can imagine that something like a new category ‘bug fixes’ or similar can help and that you only use that category for these kind of topics? And you can decide yourself if it's read only or if people should be able to reply to it? You can even decide on it per post.
If you ever had a profile with us, there's no need to create another one. Don't worry if your email address has since changed, or you can't remember your login, just let us know at community@gainsight.com and we'll help you get started from where you left.
Else, please continue with the registration below.
