New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Backend Listing Filter dependencies #6649
Comments
It's not really a bug. The filters just check which values are in the database - and not an intersection of all filters. |
I guess it´d be a good feature, wouldn‘t it? |
No it wouldn't because then you can easily end up in a dependency state that you cannot resolve anymore without resetting all the filters. Think of how this would work with 5 filters enabled at the same time. Everytime you would update any of them, any of the other 4 could become invalid because the option you selected does not have any results anymore. Which one wins now? Classic filter issue. So imho we should definitely not change this. |
I don't see the problem exactly. From a user perspective this is exactly what I expect when filtering lists.
What is happening currently?
In this example it is obvious that it does not match Germany & Belfast. The feedbacks from plenty of our customer editors is the the current filtering method is not intuitiv nor logical. |
Labeling this as feature request, because it certainly is not a bug (even though you might consider it non-optimal. |
Affected version(s)
4.13.35
Description
I am not sure wether this ist a bug or a feature.
The filters in the backend list do not depend from one another.
For example, when filtering members by Country (Germany), there are still all cities from all other countries available.
Doesn't seem to be logical.
The text was updated successfully, but these errors were encountered: