Kanban Board

what is the sense of the "DIY" option?

It would really be nice to have plan mode kanban. Even though not strictly following the "process" its nice to be able to chunk issues into larger version, say 2.3, then use kanban to push out successive release within 2.3 (eg, 2.3.1, 2.3.2) where each release is whenever we want. The relase... works great for kicking out the minor releases, but some level of planning at the x.x level is nice as well.

So of course we can do the above just by editing individual issues, but that is very clunky. Drag and drop to versions was sooo nice in classic mode. (Now I have my team wanting to go back to Pivotal because the great feature of planning in GH pre 6.0 is gone.)

I fully agree here on adding the planning function into Kanban.  It is a wrong assumption to say there is no planning in Kanban.  The fact is, in an enterprise setting, releases go to System Test, then Acceptance Test, then to Production.  These groups are not always agile in how they work, and indeed, what is quite prevalent in the real world is a mixture of agile and more waterfall approaches.  Even though a development team may find Kanban to be a great way to keep work flowing out into releases that go to ST, the test team may still do traditional preparation of test scripts for expected changes.  Managers want to know what features they can expect on a certain date.  For this, assigning Issues to Fix Versions has worked great, but when we switched from Scrum to Kanban, the ease of assigning versions was lost.

Basically, I would suggest that Greenhopper SUPPORT methodologies, while not necessarily FORCING exclusive use of that methodology.  It should be possible to use a hybrid of both Scrum and Kanban, since this is what often works best in the real development world.

I would also like to plan in kanban using greenhopper.

I'm another one voting for a form of planning mode in Kanban.

For me the target would be to be able to drag/drop issues into buckets (for want of a better word) when they are all related.  Again, I can do this by manually linking issues, and maybe what I want isn't a plan mode function, but it seems a very useful feature to have.  Maybe the ability on the Greenhopper Work panel to drag items into other items as a way of creating sub-tasks.

The issue is that (while using the kanban board to control production support), sometimes a major failure can lead to lots and lots of closely related tickets.  Being able to group these would make management so much easier, and once the cause is fixed, cleanup would be easier without it getting in the way of other urgent tasks that may appear (nothing like trying to notice one urgent issue amongst 120 "OMG my data isn't what I expected" reports.)

One more vote for planning view available in Kanban-board.

We have Scrumban-ish process and as Ken Kopelson already mentioned, planning exists in Kanban too. I also agree with him on support / forcing methodologies. As a workaround for disabled plan mode in Kanban we have both Kanban and Scrum boards set up and we use Scrum plan mode to groom our backlog and then Kanban work-mode for visualizing WIP (scrum work view is empty as there is no ongoing sprint). This solution works for now, but it is quite annoying to use.

Is there anyway to add policies to kanban columns? I want to have them visible somewhere on the board at all times. They're a bit piece of kanban and there doesn't seem to be any basic functionality for it. I tried writing it right into the column title, but that just looks awkward and doesn't really allow for much text. 

Also - I agree about the plan mode for the kanban board. I think I would be more okay without it if there was better support for epics with kanban.