@Chris Tooley Unfortunately https://confluence.atlassian.com/display/JIRA051/JIRA+5.1.8+Upgrade+Notes says: "JIRA 5.1.8 does not work with GreenHopper 6.0.4 and earlier"

I would prefer GH Classic and Rapid Board being separate packages.

That's not how i meant my comment chris.tooley@savvis.com; Sure, the new boards could use a better way for release management, but if you want to promote the Classic Boards back up, and demote the Rapid Board, why not stay on 5.10, until the 'issues' are fixed?i'd rather see Atlassian resources towards less temporary solutions. No harm intended

Now, that's not fair Edwin. The new boards are far superior to the old for iteration and epic planning. Besides, I do run 5.10 I'm our production environment, however I need to prepare for 6.X if we'll ever move there in the future.

Why do you guys install new version of Greenhopper then?The new versions do not add much functionality to the classic tools; i'd settle with 5.10 for now if i were you.

This is also duplicated by an internal ticket from myself which can be seen by Atlassian: https://support.atlassian.com/browse/GHS-5399: "Classic Board entry in menu punishes user"

+1 (for 2,000) users.

RapidBorad went out of labs WAY too early - look at all the frustrated customer comments!!!!

our request GHS-6160 was also rejected over night

I completely missed the comment by Shaun. I understand your rationale Shaun, but it is disappointing. It means we will continue to have to struggle with 5.10. I can't keep making "incremental" steps to functionality with my users, it's not they're primary goal to use JIRA/GreenHopper, they use it as a tool to meet their primary goal. I can appreciate the amount of effort and work you and the team have put into the new Boards, but there is simply too much functionality missing from them to make them usable on their own. The new features would be fantastic, but not at the expense of a short-term training solution for 500 users.

Shaun, I am not sure if you perceive the situation correctly. Many users are complaining currently in my organisation about that.

Is this the right way to solve tickets? People cannot even vote for it?

cheers
Stefan

Hi Chris,

To be honest we won't be doing this because we'd rather fix the root problem, release planning in the new boards. We plan to look at release planning in the near future.

Are you aware that if a user has been using the Classic Boards and they just click the "Agile" word itself rather than the arrow next to it they will jump straight back to where they were? This works with all of the Agile boards (i.e. if I always look at a particular board just clicking the Agile menu will take me straight there). You can actually go further than this and get your users to set their JIRA home to Agile (in the Profile menu). They will then go straight back to their last Agile board when they log in to JIRA.

Thanks,
Shaun

I can absolutely support that, I myself have asked since weeks that it was bad decision to move the old boards to "classic" where they are harder to find (see https://support.atlassian.com/browse/GHS-5399). It resulted into a load of support and explanations on my side.