With a Next-Gen Project how do I manage Epics with a Kanban Board and Swimlanes?

unknown

I have been reading some documentation (including internal Atlassian stuff) on managing a Portfolio at Scale.  In both articles (and the video from Rosetta Stone) they were managing epics in a self contained Roadmap project and using a Kanban approach to manage them.

We created a new Next-Gen project to do this -- and created epics -- but I see no way to actually manage them in this style at all.  Our desired flow is something like

 

Raw Funnel -> Accepted -> Analysis -> Grooming -> Development

Where after "Raw" everything is prioritized (in order) and kept in swimlanes (via Label).  Well, that is the desire -- I don't see how this is possible with Next Gen or am I missing something very obvious?  

I am not sure the Roadmap option is appropriate (or even usable) for this style Portfolio management? 

 

Petter Gonçalves

Hello Steven,

Welcome to Atlassian community.

I understand that you would like to prioritize your \Epics in a next-gen Kanban board, Splitting them in swimlanes organized by labels that will define their priority. Is it correct?

Next-gen projects are simpler and limited templates built for those customers who needed a simpler and straight to the point solution, so I'm afraid it doesn't have two of the required features you want:

1 - Epics can only be managed in the Roadmap feature, not in the Kanban Board

2 - Next-gen swimlanes can only be configured by Epics, Assignee or Subtask. but not Labels. 

That being said, I recommend you to use a Classic project of JIRA software, where you can customize your Kanban board to display Epics and your swimlanes to be configured by JQL, where you can use the label field.

If need help to configure the mentioned settings, let me know.