Forums

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

Previous standard filter no longer availibe - why???

Jeppe Vilstrup Holm October 14, 2021

Major mistake by atlassian. Give us back our label filter! The old model worked with member assigned was above the label. When I click me and one or more labels, I don't want "any" or "exact", I want me + plus all labels with me. Why would you remove the previous standard filter????? Whyyyyyyy??????

1 answer

0 votes
Raymond Wang
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
October 15, 2021

Hey @Jeppe Vilstrup Holm, thanks for the feedback! If you're hoping to filter for cards assigned to a member in addition to all of a set of labels, I believe the "Exact match" filter should suffice. Can you clarify your use case to help us understand where the gaps in your workflow are?

Jeppe Vilstrup Holm October 17, 2021

Often a card has more than 1 label (sprint (whitin 2 weeks + scrum(currently active)). So exact is not working for me when I want all sprint cards, I will not get a card with 2 labels. This was the standard search functionality. Members over labal. How could you remove the old standard way?????

Jeppe Vilstrup Holm October 17, 2021

There can also be more than one member on a card. I can see from a programming aspect that any or exact are the simplest and also the easiest to explain. What I'm looking for is filter first on any member, secondly from the first result pool any label. Otherwise we might have to drop trello, all 50+ premium accounts.

Raymond Wang
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
October 18, 2021

Hi @Jeppe Vilstrup Holm, thanks for the clarification. I totally hear you that your workflow was negatively impacted by this change, so we're going to change the logic for "Any match" to support selections across different categories, like it was before. This should be resolved in a release slated to come out either later today or early tomorrow.

You're right that one of the big challenges of this release was striking the intersectionality of simplicity and the ability to be explained, and "Any match" felt right in development in comparison to "Matches any labels and any members". However, that's no excuse for breaking an existing workflow that you were reliant on, so we'll take it back into the shop and hopefully continue to find that balance in the future. Thanks for the feedback and explaining your use case!

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events