Sub-Task incorrectly under "Issues without epics"

[Etienne Viljoen]

We use a Kanban board with Tasks and Sub-Tasks, with Epics as our swim lanes. This works pretty well. However, during stand-up we filter by Assignee. The way we work, one person can be assigned to a Task, but another person assigned to some of the sub-tasks of that Task. When not filtered, tasks and sub-tasks are correctly displayed in swim lanes according to the Epic that the Task belongs to. But, when the assignee of the sub-task filters to show only their issues, sub-tasks that belong to Tasks that are assigned to other people drop to a swim lane at the bottom labelled "Issues without Epics".

Am I doing something wrong?

[Nic Brough -Adaptavist- · Accepted solution]

No.

You have nothing wrong.

Sub-tasks are a part of their parent issue, not separate items, and you can always state that "sub-task X is part of issue Y, which is in Epic Z, so, X is a part of Epic Z"

While Jira is good at enforcing the right structure, it's really bad at reporting on it.  A sub-task is always part of an Epic when its parent issue is in the Epic, but Jira won't tell you that without a lot of faffing around. 

It's the same with sprints -- utter nonsense that a sub-task is not part of its parent and hence in the same sprint, but a report on "sprint = X" fails to include them.

Jira does not do sub-tasks well.  There's an essay on the history, I won't bore you with it.  The (short, blunt and not really too helpful) answer here is simply "ignore sub-tasks".  Just think of them as a part of a bigger thing, and concentrate on that bigger thing.