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; } } }

How do I show sub-tasks on Kanban?

Emily Thraen

I realize that this question has been asked before, but the answers on those posts did not solve this blocker for me.

BACKGROUND: Our Content team makes use of a private Kanban board to see what everyone is working on amoung our products. The products use Next-Gen. The Content team utilizes sub-tasks to illustrate their workflow: IA, write, edit, medically review, etc. Kanban filter is assignee in (list of content members)

I have tried the below combinations to make it to where sub-tasks show on the swimlanes:

Adding AND issuetype in (Task, Sub-Task) to the end of the board's filter
Switching what the swimlanes are based on between "Assignees" and "Story"
Creating quick filters: issuetype in (Sub-Task) as well as trying issuetype in (Task, Sub-Task) so as not to exclude the parent task

Accepted answers

Emily Thraen

Was just using the wrong query: "Subtask" should be used as opposed to "Sub-Task". OR...be like me and use all of them: assignee in (-people-) AND issuetype in (Task, Sub-Task, Subtask).

Cheers

All comments

Chris Buzon

Two parts:

1) the JQL query that drives the board must return the results you're expecting, or it's not the right query (meaning you should see the expected subtasks when you just search for issues using the same query that the board uses).

2) Swimlanes area. You'll get different results depending on which setting you use here. Try changing this to Queries and see if that fixes it for you.

Chris Buzon

In case point 1 is confusing - your JQL query must return the results you're expecting (all of them, including subtasks) when you plug the board query into an advanced search like this:

Emily Thraen

1. Should, yes. But I'm not... The query seems fine when I use it outside of the board though. If you read my query in the description I include tasks and sub-tasks

2. Switching the swimlane to queries did not work either. I used issuetype in (Subtask, Sub-Task)

Chris Buzon

Can you paste the whole query here? I don't need the names or real project keys, but I do want to see how your query is structured as a whole. In theory, you don't need to specify issuetype in the main query at all - you could use the subfilter to remove the ones you don't want to see.

It's also possible that the sub-filter has this (default) which may be further messing with your board.

Emily Thraen

Was just using the wrong query: "Subtask" should be used as opposed to "Sub-Task". OR...be like me and use all of them: assignee in (-people-) AND issuetype in (Task, Sub-Task, Subtask).

Cheers

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-software

jira-software-cloud

kanban

sub-task