"Hierarchical Boards"

[Paul Adams]

In the introduction (on the Home page), you have the statement "Support for one project on more boards (enables creating hierarchical boards)". Can you elaborate on this a bit more please?

I have tried creating multiple boards and adding the same project, but the effect is like actually having a completely separate project. The only reason for using the same project on a different board seems to me to be that you can select tasks on multiple boards by selecting just one project filter. I thought it was going to be possible to see tasks from my project as different views on different boards (assuming the same state names were used of course).

Ona  separate point, is there anywhere I can see what features are going to be appearing in which versions along with an approximate time frame? I saw some mention of Tags, but I didn't find any explanation of what to expect with this feature. The feature I am looking forward to is role based permissions.

I only installed Kanbanik yesterday, but I am already impressed with its simplicity of use and the configurability of the workflow. I also administer a VersionOne server as well as a simple freeware iceScrum server. Of course VersionOne is the most configurable and is the right tool for corporate projects, but iceScrum and Kabanik both have great features for small projects/teams. Currently without the role based permissions, Kabanik can only really be used as a personal Kanban board as everyone who is a user on the server can do anything, but as soon as role based permissions are implemented, I think it could be really useful for small department based projects that do not have the complexity or large teams of our customer based projects. Currently we are using iceScrum for the smaller projects, but I could see that changing due to the configurability of the workflow.

Keep up the good work.

Paul

[jel...@gmail.com]

Hey Paul,

the "hierarchical boards" are really meant only as to have completely different flows - e.g. on higher level board you really have different workflow and different tasks than on lower level. It is more a logical grouping that the same project is assigned to different boards. It can be used for example that you set your filter up to see only certain project and than you can see it from different levels of the hierarchy - all in one page.

About the time-frames and planning. Well, no, no actual planning. Normally, each release I do 3 things:

- Implement one bigger task (this release the bigger task will be the tags - will elaborate a bit more later)

- Enhance the performance a bit (now it is quite fast already but there is still room for improvement)

- Enhance the design / UX a bit. It is still quite ugly but the current master branch I kind of start to like

But I have absolutely no time estimate since I have about 2-3 hours a week I can work on kanbanik which is also not certain. With this it is impossible to do any kind of time promise... Currently I'm more or less finishing this iteration with the tags implemented - if you wish I could give you an "unofficial" build somehow or you can build it from sources by yourself - it is simple and there should be no problems.

The bigger feature of this release, the tags: It is only about having a possibility to attach some "tag" to a task - e.g. a free text like "blocked" with some colored background or some image. You can assign as many tags as you want to one task and mix the free text with images. You can set an "on click target" - e.g. if you click a tag than a certain page will be opened.

I'm personally using it with my gerrit-to-kanbanik integration (https://github.com/jelkosz/getuka) (gerrit is a code review tool) where I have couple of tags assigned for each task like "code review +1, jenkins -1" etc and than one tag with link which if clicked the specific gerrit page opens. Very useful for me.

Since suddenly more and more people are asking for the role based permissions for kanbanik, after I release this version, for the next iteration the big task will be the role based permissions. 

Thank you for the comments,

Tomas

[Paul Adams]

Hi Tomas,

Thanks for the quick and comprehensive reply. I will keep an eye out for your progress with Kanbanik and try out each version as you release them.

All the best,
Paul