Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Quick filters not working on subtasks anymore since a couple of days

richard de bock
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
July 22, 2022

Setup

In the Active sprint board we have Quick filters set up to filter tickets for a specific platform. We have a filter for 'iOS' and a filter for 'Android'. The query for a filter is simply 'summary ~ iOS'.

Then, in the sprint we have story tickets, with each story having 2 subtasks, titled 'iOS' and 'Android'.

Schermafbeelding 2022-07-22 om 11.08.28.png

 

Issue

We've been using the quick filters for years now, but since a couple of days the filters aren't working for us anymore. The filter only seems to show 'main' tickets, that fit the conditions, and does not display the subtasks.

So a ticket called 'Fix .....' with subtask 'iOS' does not show up in the 'summary ~ iOS' filter, but a ticket called 'Fix iOS .....' with subtask 'iOS' does show up in the filter.

A couple of days ago both cases would show up when using the iOS filter.

Any idea's what we can do?

1 answer

0 votes
Walter Buggenhout
Community Champion
July 22, 2022

Hi @richard de bock and welcome to the Community!

This suggestion is not related to the main/sub-task behaviour that you describe, so it may not be a solid fix. However, I would recommend to use e.g. components for iOS and Android rather than relying on the summary. It would definitely be a more structured approach to what you are trying to do and even may offer you some reporting capabilities you don't have today as a nice additional benefit.

Hope this helps!

richard de bock
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
July 22, 2022

@Walter Buggenhout thanks for your suggestion, I see where you're going, but filling in the component is just more work than simply typing iOS / Android as the subtask name, so we choose the simple approach. But we could always look into automatically setting the component field when creating a ticket with such a name in the future. Thanks again for the suggestion, but it indeed doesn't solve our filter problem.

Suggest an answer

Log in or Sign up to answer