nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Kanban board with Epic swimlanes not showing grandchild tasks properly

unknown

I have the following object structure: Epics contain a few Stories. Each Story contains several Tasks. If I create a Kanban board and configure the board to use Epics as swimlanes, then all the Tasks show up in the "issues without Epics" swimlane.
The query is simple - just everything that's unresolved or resolved in the past 2 weeks:

project = XX AND (resolutiondate is EMPTY OR resolutiondate > -14d) ORDER BY Rank ASC

I have configured the board to use swimlanes by Epic but these swimlanes contain only the directly linked Story objects. The grandchildren (the Tasks in the Story) do not appear in the Epic swimlane. From a conceptual standpoint, they should.

Has anyone figured this out? Is this solvable by using the Links Hierarchy plugin? Seeing links is one thing but having the Kanban board reflect the indirect mapping from Task to its parent Story to its parent Epic is absolutely necessary.

Accepted answers

Petter Gonçalves

Hello @[deleted]

Welcome to Atlassian Community.

Per your description, I believe you have linked your Epics issues to Stories and the Stories to Tasks, expecting the tasks to appear under Stories and Stories under the Epics when using the Epic Swimlane of Jira Boards. Is that correct?

Please, allow me to bring you some concepts so we can better confirm we are on the same page here:

Jira works only with three hierarchy levels:

Epics -> Standard issue types (Story, Tasks, Bugs, etc) -> Sub-tasks

That being said, the Epic swimlane of Jira boards only displays sub-tasks under the related Stories/Tasks of the Epics. Any kind of link between standard-issue types (like Stories and Tasks) is not considered a hierarchical link and it will not be displayed under each other in the swimlane.

That being said, we recommend you replace your tasks with sub-tasks under your Stories to achieve the layout you want:

Screen Shot 2020-01-17 at 19.26.07.png

The scrum-31 in the screenshot below is a Story with sub-tasks on an Epic Swimlane:

Screen Shot 2020-01-17 at 19.28.56.png

Let us know if you have any questions.

All comments

Petter Gonçalves

Hello @[deleted]

Welcome to Atlassian Community.

Please, allow me to bring you some concepts so we can better confirm we are on the same page here:

Jira works only with three hierarchy levels:

Epics -> Standard issue types (Story, Tasks, Bugs, etc) -> Sub-tasks

That being said, we recommend you replace your tasks with sub-tasks under your Stories to achieve the layout you want:

Screen Shot 2020-01-17 at 19.26.07.png

The scrum-31 in the screenshot below is a Story with sub-tasks on an Epic Swimlane:

Screen Shot 2020-01-17 at 19.28.56.png

Let us know if you have any questions.

unknown

@Petter Gonçalves this is a clear explanation, and it makes perfect sense. Thank you!

Petter Gonçalves

You are welcome, @[deleted]

Have a nice week.

Tzirel Shaffren

UPDATE: By experimentation, we found that if the Standard Jira is marked as "Reported", but the subtask is marked as "Development", neither the Standard Jira nor the subtask are displayed in the Epic's swimlane. However, if the Standard Jira is marked as "Development" (which is quite reasonable if it has a subtask that is in "Development", then the subtask DOES appear in the swimlane, and, actually, quite nicely with a frame around the tile indicating to which Standard Jira it belongs.

ORIGINAL QUESTION: The above answer doesn't seem to work for me. Has anything changed in the handling of sub-tasks since this was written? We are set up as described, but the swimlane (set to Epics) is not showing the subtasks.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud

kanban