Community moderators have prevented the ability to post new answers.
In JIRA Agile, it is possible. Just go to configure board -> Columns and drag and drop as many statuses as you want in each column.
Is there a status for this request that you mention @Nic Brough [Adaptavist] do you maybe have a ticket number for it so I can follow the progress? Splitting up columns is something I am looking into right now and would be interested in seeing when this might be possible in Jira.
@Nic Brough [Adaptavist] you mention is not YET there. DO you know more? as said by @Brook Warnerhaving this sub columns is a fundamental concept in Kanban. The whole concept of the pull system relies on this.
We are currently a Redmine Agile plugin user want to move the teams to the atlassian suite. The Redmine guys have solved this via the name of the Status diveded by collons. It's a bit hacky but works.
This would be in the Sample above to have the following Staus configuration
The Board renders this as seen in the picture
As we now we can as many status we want in Jira Agile,. Very first Hack for "grouping" them could a option to give columns a color. Is this possible?
To have Ongoing/Done for each activity is important. Why?
The whole idea of Kanban is to have different states which illustrate a journey of a task and most often different columns are carried out by different teams. Unless there is a Done column, the next vertical wouldn't be aware of picking up things. Since JIRA needs to map ticket statuses to columns, it can only be achieved by having Dev:Ongoing, Dev:Done, QA:Ongoing, QA:Done etc. Surely, it can be done by having independent stautses mapped to columns, but being able to achieve the picture gives a great aesthetic touch. It would need some logic though like Dev:Ongoing means an Ongoing state of Dev.
It seems to me this same question has come up in different ways over the last four or five years and not to have any kind of resolution or "fix"...
For me I would "express" it as being able to replicate the same status in multiple columns. I want to have my Kanban columns follow the required organisational workflow e.g. To Do - In Planning - In Design - In Consultation - In Implementation - Done
But within each of the workflow phases of Planning, Design, Consultation and Implementation I want to be able to have the task status reflect our functional process of "In Progress", "Awaiting Review" (this is different to consultation), "In review", "Blocked", "On Hold" and "Handover". It's basically like a workflow within a workflow, but the nested team workflow is applied uniformly across the main organisational workflow.
I know I could make four versions of the status e.g. "Planning in Progress", "Design in Progress", "Consultation in Progress" etc. but that is really cumbersome and long-winded and kind of defeats the object of being able to break down the workflow with columns and then apply multiple statuses to a column?
The only other alternative I can think of is to have different boards for each of Planning, Design, Consultation and Implementation Phases where we use the functional team process as the column name, but that doesn't work for my team as different workstreams/sub-teams are at different stages of the organisational workflow at different times and we need a Kanban that shows the view across all workstreams instead of four separate boards, or some on the Planning board, some of the Design board and no-one on the Consultation board yet etc. Some are "In Progress" with Planning and some are "In Progress" with Implementation. In my experience this is the case the larger a project becomes, the more people who are involved and the more wide-ranging the program/portfolio is.
Maybe what I need, especially for large, complex, organisation-wide projects is to collapse boards into one another or to reflect nested processes in one overarching, high-level board so I can get a wider, cross-company view...
Whatever the case, it seems to me there is demand for it, so even if Atlassian disagrees with the approach, surely customer demand and need should drive the development of a solution?
>For me I would "express" it as being able to replicate the same status in multiple columns.
Please, don't express it that way. It is not what we're talking about here, and it would make your boards complete nonsense.
Look at an issue. Is it "in progress" or "in progress"? Do you really want it to appear twice on a board at different stages in the process?
What we want here is for boards to group up columns together. We do not want the issue status and hence workflow to become completely useless.
The nested workflow sounds overloaded but in essence the doing and done sub columns are exactly that. Even it is the most simple workflow you can imagine.
Further, if you do Kanban in practice you are forced with blockers which needs to be parked because of external dependencies. This would be another sub state.
These states often are placed on extra areas of the real physical Kanban boards. There not many online Kanban boards support such flexible layout. LEANKIT is one of them.
In jira I assume that jql is the right tool to select the task for all such columns. There are just a few layout options missing. Like grouped or merged columns.
Hello, Community! My name is Gosia and I'm a Product Manager on Jira Server and Data Center here at Atlassian. Since 2002 when we launched our public issue tracker, jira.atlass...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs