Kanban view - with lots of statuses is too squashed

[Katie Hudson]

Hi there,

I want to use the Kanban view for my project - and have lots of 'statuses' rather than just 'dev, test, deply' - I want to have about 15 columns.

Currently, when viewing the Kanban board, all the columns are squashed into the screen, and so are horribly thin/ don't allow me to see any detail (or even the title) of the columns. I want to be able to see the details of each column - and therefore obviously not see all the columns in one view. I was expecting ot need to scroll to the right to see further columns - and this is what I am looking for.

Is this possible?

Thanks,

Katie

[Katie Hudson · Accepted solution]

Having now entered all my columns (with great difficulty as in this view they are even more squashed) - I can literally see no detail - and editing is nearly impossible. See below.

I realise this is partly due to the 'settings' menu on the LHS, which creates a huge indent, but there is no way of changing that enough to make a difference to my issue.

Is this the extent of editing the Kanban board on Jira - or am I missing something? There is no way to scroll right still - and It's therefore unmanageable for more than about 6 columns.

I want to use JIRA for our project management - but doesn't seem it will be possible if the UX is this terrible with Kanban.

Can you please help?

Thanks,

Katie

[Kirstin Seidel-Gebert]

Hi Katie,

IMHO having a workflow with so many statuses is not very standard agile. I think JIRA is not designed for that.

What you can do is combine multiple (similar?) statuses into one column. As soon as you drag an issue onto such a combined column, a region for each status that resides in this column gets visible.
You can decide which status to transition to by dropping the issue into the matching region.

I can't add a pic because we don't use this but I've already seen it working.

Cheers,
Kirstin

[Deleted user]

Who said anything about agile? OP certainly didn't.

And what of the folks who want to visualize where they are now? And work towards "agility"? Is it a good thing to not promote those folks' ability to pursue that?

To Do -> In Progress -> Done 

works, but if that's "Not us", then should something like Jira permit that to be possible?