Your comments

See attached image for your review.
I like this idea. Being able to collapse a theme cuts down on scrolling and improves visibility of themes that need attention.

Not sure if the ability to remember collapsed themes is important. I do think it would be great if the stories in a collapsed theme are excluded from tabbing actions. Once expanded they would be included in tabbing.

Thanks!
Click to move...ahhh got it! Took me a  minute but it makes sense to do it this way.


Part of the trouble I had was the help bubble is partially covered up by another bubble that says "undefined". example http://screencast.com/t/1SiS4CFwH8Ng 

I like this suggestion and understand why there's a need for it.   Drag and drop ranking would be really slick, even if it's only ranking features within themes.

That aside, grouping and ranking stories by themes is great if you are allowed to complete an entire theme before moving on to the next highest ranking theme.  Not all teams have this luxury; however, especially service-based teams.

Having the ability to rank at a feature level vs. themes level gives a PM the ability to see the highest customer affecting features across all themes. These can be easily identified and moved into Kanban without being impeded by features that have lower customer impact. 

Ultimately, I would rather see this type of ranking incorporate severity and priority; severity being customer impact (1=high, 2=med, 3=low), and priority (1=need, 2=want, 3=bonus). It would be great to see the overall list sorted by severity.priority (1.1, 1.2, 1.3, 2.1, 2.2, etc) as an OPTIONAL view and OPTIONAL export type.