How to group stories under epics in a Kanban Board?

[Kunnagh Scott]

How does one order the issues in a Kanban Board column so that the Epic-Story hierarchy is respected?

i.e.:

Epic 1

- Story 1a (Epic Link - Epic 1)

- Story 1b (Epic Link - Epic 1)

Epic 2

- Story 2a (Epic Link - Epic 2)

etc.?

TIA

[Alexey Matveev]

Hello,

You should go to the Board cofiguration then go to Swimlines and in the "Base Swimlanes on" field choose Epics 

[Kunnagh Scott]

Thanks for that - good answer, but we already have our swimlanes based on queries - we use labels to split work into one of four sub-categories that the team handle.   Is there a way to do this grouping within the lanes?

Thanks

[Alexey Matveev]

No, you can not group within swimlanes unfortunately.

[Kunnagh Scott]

OK - we'll have to manage!  Thanks for your responses - appreciated.

[Paul Taylor]

this is less of an issue now as the new roadmap view in cloud allow grouping of stories under the epic .. it's not a swimlane on the board but it really helps the context

[Paul Taylor]

it's not strictly the case that you cant group, it's a work around but we have been using this for organizing our epics under portfolio initiatives. It is a slight maintenance issue but works for larger pieces of work that are consistently used. "Parent Link" in linkedIssues(EB-1491) . The first time you use the swimlane you have to link the initiative ( parent ) to the child (epic) and then back the other way .. so link both ways .. after than every new epic that is given the same parent link will show up under the swimlane for that initiative.   There must be an equivalent for epic and story likely it will be "Epic Link" in linkedIssues() .