Fixed Issues in Jive 6.0.2 | Jive Community
Also noting Known issues in Jive 6.0.1
I thought I would discuss a little bit about our process here in the community based on the interesting discussion we were having in other streams (Donna Garber, flag me if this is inappropriate)
As you can see, we're on version 6.0.1, and 6.0.2 and .3 etc, are not really about adding new features, but rather fixing known bugs (yes some new features do appear but more tweaks).
Much like other Jive communities, HDS has spent some effort in customizing the community to fit the needs of the audience (we have several here). And when you customize you need to take that into consideration when you move to the next point or full release (It becomes incrementally harder the more you customize).
Part of the 1.5 release in August that Nick mentioned will be this kind of evaluation: Do we go through the effort o upgrade to the next point, do we patch the current release or do we say it can wait because it isn't high priority/high value to fix right now.
Also in this mix is the consideration: Is the bug/feature ours, or does it belong to Jive. What would it take for us to fix it. If it's ours, that's usually something we can address. If it's Jive's we have this larger conversation.
When we look to Jive 7, then you're going to see big release notes and lots of new goodies.
Very insightful Roguen. I've work in environments that had heavy ERP customisations made, so I guess it's along the same lines with the same types of challenges. Can you contribute upstream to Jive? Or is it closed source and you can only work on custom modules?
We unfortunately cannot contribute upstream on this, only make recommendations around features we would like to see.
Jive uses their own polls when it comes to roadmap recommendations, so I'll certain we'll be asking for some added "voice" when it comes to things we would like to see in the core product.
A lot of what we do as customizations may not make a great deal of sense as a core product either. For instance, we have a mechanism that with certain groups, when you join you are given added access to added spaces in the community (sorry for the Jive terminology here). This is really an edge case which would add complexity for the other 99% of community admins who don't even know why they use it.
The site theme is also another one of those areas that is going to vary dramatically from community to community.
To address this upgrade issue Jive has introduced something new though: Jive Cloud.
The cloud has the major added benefit of always keeping the community up to date with the latest quarterly release.
It also had the major drawback of not allowing for any customizations to the community (functional or theme-wise). At least not in the way that happens now. We're hoping to see some headway on this front if we want to even consider it here, but that's a separate conversation
The lack of customisation is almost always a limitation of a managed hosted solution.
From a user perspective, I think are working out well with the current implementation, sure we have a few small issues, but teething problems are always expected. I think you and the rest of the team have done a great job with the deployment and backend management.
Hello Cris Danci,
I have found by joining the jive user community, you can advocate for new features and interact with fellow users regarding how they have configured their environment.
Welcome back Lauren Klein
Thanks for letting me know. Ill look at joining at some point..
Retrieving data ...