Skip to main content
Question

How are you managing non-GA release notes in your Community?

  • February 20, 2026
  • 2 replies
  • 0 views

ryanne.perry

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.

2 replies

Forum|alt.badge.img+3
  • Helper ⭐️⭐️
  • February 20, 2026

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.) 

Forum|alt.badge.img+3
  • Helper ⭐️⭐️
  • February 20, 2026

I also know Gainsight itself does this here with this Known Issues Tracker that is Jira-based!