We make heavy use of version hierarchies and as far as I'm aware they can only be configured from within the Planning Board view. With the recent upgrade of GreenHopper we are now notified that the Planning Board is now a 'Classic' part of the product and is being deprecated. Does anyone know what will happen to the version hierarchy feature if the Classic boards are removed?
Hey, check this comment from Shaun Cloves (Atlassian):
Aug 29, 2012
We would like to revisit release planning in the future, but we're pretty sure it won't be hierarchical versions because they joined the concepts of sprints and releases rather than allowing the two to be related.
In any case, we haven't removed any functionality at all, you can continue using the classic boards with the hierarchical verisons if you wish.
Ok, the original question was asked and answered in 2012. It's now 2014 and I want to see if there's any new direction/thought on this topic.
We also make use and depend on version hierarchy. It continues to work for now but I keep seeing references saying the Classic Board is going away. The only thing we use on the Classic Board is defining the version hierarchy as we add new versions. Without version hierarchy, a whole bunch of our filters that reference parent versions will stop working.
Is the version hierarchy capability and behavior going to be migrated to core Jira? Now that sprints and fixVersion have been separated that's the most logical direction this could take. I sure hope version hierarchy doesn't just disappear one day when Atlassian puts a new release out to AOD.
Can someone from Atlassian who knows the product roadmap respond with an update?
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot