Kevin, I think you are absolutely right on the money here. I think this is the reason that the documentation team started transitioning the documentation into Jive, rather than off in a separate side system. I know they've commented on this recently about when they will update the documentation ... but it is not 100% clear to me at this moment. Honestly haven't thought about it. I do not think it is an unreasonable request that we close the loop on some major bugs filed against these versions. I think the problem comes in knowing which of the versions are affected. (i.e. customer reports in version x.y.z ... but does that issue happen in x.y.y or x.y.x?) How far do we take this research for each issue? How often do we make these updates? Weekly? As-Needed? Are the customers expecting to see a diff of the changes and/or is there a weekly blog post here to advertise?
This may be a separate conversation...so if this blows up...I will probably branch this discussion.
I think that having the list visible and at least with which versions people have reported seeing it would also help reduce duplications. If the support engineer is working on the problem, I could “vote” on it similar to an idea instead of creating a new one.
Configure your Jive Community experience by selecting a track. We'll use this track on the homepage to show you relevant content and help you find resources quickly. You can change your track easily from the homepage or your profile.
As a community manager, you're an ambassador for your Jive community as you build places, curate content and engage with fellow community members. To help you go further with your site, we'll share success stories and other resources.
Whether considering a new purchase or working on an upgrade, technology managers need insight on the best ways to implement a community and learn more about the various upgrades in software releases.
An effective community starts with sound business strategy. As your community matures, you'll want to learn and share best practices for implementation and continued success.
Whether you're a developer, system administrator or a designer, you need insight on building a great user experience for your Jive community. Get the scoop on theming, API's, upgrades and more.
We've got a special area for partners to get essential information and best practices they need for describing and selling Jive to potential customers.
Whether or not you have a specific role in your Jive community, this track highlights areas of interest to Jive users such as training materials, community best practices and an opportunity to network with other customers.