{"action":"created","issue":{"url":"https://api.github.com/repos/fguillot/kanboard/issues/530","labels_url":"https://api.github.com/repos/fguillot/kanboard/issues/530/labels{/name}","comments_url":"https://api.github.com/repos/fguillot/kanboard/issues/530/comments","events_url":"https://api.github.com/repos/fguillot/kanboard/issues/530/events","html_url":"https://github.com/fguillot/kanboard/issues/530","id":54867589,"number":530,"title":"Column Grouping / Split columns","user":{"login":"elnicko","id":10612267,"avatar_url":"https://avatars.githubusercontent.com/u/10612267?v=3","gravatar_id":"","url":"https://api.github.com/users/elnicko","html_url":"https://github.com/elnicko","followers_url":"https://api.github.com/users/elnicko/followers","following_url":"https://api.github.com/users/elnicko/following{/other_user}","gists_url":"https://api.github.com/users/elnicko/gists{/gist_id}","starred_url":"https://api.github.com/users/elnicko/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/elnicko/subscriptions","organizations_url":"https://api.github.com/users/elnicko/orgs","repos_url":"https://api.github.com/users/elnicko/repos","events_url":"https://api.github.com/users/elnicko/events{/privacy}","received_events_url":"https://api.github.com/users/elnicko/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/fguillot/kanboard/labels/feature%20request","name":"feature request","color":"0052cc"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":10,"created_at":"2015-01-20T10:39:42Z","updated_at":"2016-01-21T06:49:38Z","closed_at":null,"body":"Is there a plan to implement grouping of columns? \r\n\r\nThis would be a great visual aid for implementing a well defined \"task-pull\" strategy, e. g. in software projects. Basically, it should look like this - the columns are grouped on the board so that columns of the same group are displayed next to each other, and the name of the group is displayed over the names of the column.\r\n\r\nThis is best illustrated by the following example, where there are two columns (Doing, Done) in each of the groups (Development, Test, Release etc). Currently, I create two columns for each aspect (Development, Test Release) and add *Doing* or *Done* at the end of the name. It works, however it doesn't look optimal, as the name gets too long and moves to a second line or flows over to the column next to it. A good example of this usage of a kanban board is given in this slideshare: http://image.slidesharecdn.com/kanbanboards-100328050846-phpapp02/95/kanbanboards-26-728.jpg\r\n\r\nIn terms of the data flow in the model, I don't expect it to change anything in the way kanboard works (except maybe the unique constraint on the column names), it would simply add a *visual aid*, so that project managers are able to add more structure to the board and streamline processes."},"comment":{"url":"https://api.github.com/repos/fguillot/kanboard/issues/comments/173476113","html_url":"https://github.com/fguillot/kanboard/issues/530#issuecomment-173476113","issue_url":"https://api.github.com/repos/fguillot/kanboard/issues/530","id":173476113,"user":{"login":"tvriend","id":13728151,"avatar_url":"https://avatars.githubusercontent.com/u/13728151?v=3","gravatar_id":"","url":"https://api.github.com/users/tvriend","html_url":"https://github.com/tvriend","followers_url":"https://api.github.com/users/tvriend/followers","following_url":"https://api.github.com/users/tvriend/following{/other_user}","gists_url":"https://api.github.com/users/tvriend/gists{/gist_id}","starred_url":"https://api.github.com/users/tvriend/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/tvriend/subscriptions","organizations_url":"https://api.github.com/users/tvriend/orgs","repos_url":"https://api.github.com/users/tvriend/repos","events_url":"https://api.github.com/users/tvriend/events{/privacy}","received_events_url":"https://api.github.com/users/tvriend/received_events","type":"User","site_admin":false},"created_at":"2016-01-21T06:49:38Z","updated_at":"2016-01-21T06:49:38Z","body":"+1 from my side as well.\r\nWe use a WIP limit for \"In progress\" and a WIP for \"Ready & In progress\" combined.\r\nWould love to see the addition of parent groups with a WIP limit and a column within the group with a WIP limit\r\n\r\n|||        SPRINT (10)          |||\r\n||| Ready || In progress (6) |||"}}