Kanban Column Limit

Hi Rob,

The limit is currently set for 9 columns if the field is not required (as it includes blank as an option) or 10 column if the field is required. 10 was chosen as a number of column for the early access to reflect the more common Kanban use case and to produce reporting that wasn't overwhelming. Is there a number that would be more ideal for your workflow Rob? We are certainly still open to feedback on the Kanban reporting features and the way our users are making use of the reports. 

I come from a bit of a JIRA background, and a nice thing about their Kanban workflow was the ability to group columns.

I have a fairly small issue lifecycle list that looks like this:

• Open - New
• Open - In Progress
• Blocked - Needs Info
• Blocked - Can't Do
• Rejected - Won't Do
• Rejected - Duplicate
• Rejected - Inapplicable
• Rejected - Unable to Replicate
• QA - Ready for Testing
• QA - Testing Complete
• Complete - Done

So, 11.  Of course I'm 1 over..  Story of my life.  haha

But this is a very simple workflow or lifecycle for a task.  This could become far more complex if you get into 3rd party review and other such things.  

I don't know what the answer could be, but I can't see how I could setup an issue tracker with any fewer steps.  I say let me use 50 columns if I want.  Why do you care if my report is hard to read?  (Note: I'm not in any way trying to be an ass.  I'm just stating a point.  Why limit it at all?  Let me make an ugly report if it doesn't factor into any additional burden for you guys.  The anger of the folks I make use the report later will force me to change it.)

Thanks for your consideration and feedback.

~Rob

Hey Rob,
Thanks for the feedback! If you'd like, you can sign up here to talk with the team developing Kanban: https://team.quickbase.com/db/bm2ktkaa5 

We put a limit in place because we worried it would be hard to use a board where lots of horizontal scrolling was required. We're working on the ability to only display a subset of columns for the next release, so that kanban builders can more easily create a report when they have, for example, 11 options.

Sam Jones
QuickBase Product Manager