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

Scrum Board should always show subtasks when using quick filter

Volker M_

Hi all,

we use the scrum active sprint board with bugs/stories and subtasks attached to all of them. Now, I want to use quick filters to e.g. only show "bugs". If I do that, the subtasks for the bug are also hidden.

Is there a way or a query so that a quick filter lists me the bugs, but also shows subtasks belonging to that bug?

Thanks!

Accepted answers

Mark Segall

Hi @Volker M_ - Unfortunately, this is not possible without a marketplace app. The closest you can get natively is by doing something like this:

issueType IN (Bug,Sub-Task)

However, if you have sub-tasks for other issue types. Those issue types will become visible again.

Nic Brough -Adaptavist-

Yes, you can do this.

Sub-tasks are, by definition, a different type of issue, so when you apply a quick-filter for "only show issues of type bug", they will vanish, because they are not bugs.

But, edit the quick-filter. If it says "issue type = bug", then change it to "issue type in (bug, subtaskIssuetypes() )".

All comments

Mark Segall

Hi @Volker M_ - Unfortunately, this is not possible without a marketplace app. The closest you can get natively is by doing something like this:

issueType IN (Bug,Sub-Task)

However, if you have sub-tasks for other issue types. Those issue types will become visible again.

Volker M_

Thanks a lot @Mark Segall - very sad to hear that. Cannot believe this is not possible out of the box. But then again, that is what I thought for many other features too...

Nic Brough -Adaptavist-

Yes, you can do this.

Sub-tasks are, by definition, a different type of issue, so when you apply a quick-filter for "only show issues of type bug", they will vanish, because they are not bugs.

But, edit the quick-filter. If it says "issue type = bug", then change it to "issue type in (bug, subtaskIssuetypes() )".

Volker M_

@Nic Brough -Adaptavist- Thanks - but that gives me all tickets, bugs but also stories (basically everything that has a subtask).

Volker M_

Thanks - but that gives me all tickets, bugs but also stories (basically everything that has a subtask).

Mark Segall

Hey @Nic Brough -Adaptavist- - I wish this was the case, but you'll still get the same result from a quick filter. It does not eliminate the sub-tasks that are part of other issue types and thus brings them back into view.

Nic Brough -Adaptavist-

Have another read of how Scrum works, and pay attention to the concept within it, that might help you understand why Jiira starts by doing Scrum and why it is hard to try to bodge it to not to.

Nic Brough -Adaptavist-

Cannot believe a scrum tool is not built to do scrum?

Why is that wrong?

Monica Swenson

@Mark Segall what marketplace Apps would support this? We just converted from Jira_Server... and were able to filter our scrum boards to a subset of stories/bugs AND have all subtasks for each by using the subtaskIssuesFromQuery JQL function. I realize that function isn't supported in cloud, and can get something similar by using issueFunction IN subtasksOf... However - that syntax isn't supported in a Board Quick Filter.

I think it's a very natural request - to see a subset of issues on a scrum board and all tasks beneath them.

Volker M_

Did he really say that?

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