Skip to content
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

Open
ThomasKettner opened this issue Dec 20, 2023 · 5 comments
Open

Backend Listing Filter dependencies #6649

ThomasKettner opened this issue Dec 20, 2023 · 5 comments
Labels
feature help wanted Issues and PRs which are looking for volunteers to complete them.

Comments

@ThomasKettner
Copy link

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.

@fritzmg
Copy link
Contributor

fritzmg commented Dec 21, 2023

It's not really a bug. The filters just check which values are in the database - and not an intersection of all filters.

@ThomasKettner
Copy link
Author

I guess it´d be a good feature, wouldn‘t it?

@Toflar
Copy link
Member

Toflar commented Dec 21, 2023

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.

@ThomasKettner
Copy link
Author

I don't see the problem exactly.
What is the issue with 5 active filters and resetting them when you don't get any results left?
In my opinion it is a classic AND filter situation where only results are listed when ALL parameters are fulfilled.
There is no cross filtering and no "invalids", there is just no more results left.

From a user perspective this is exactly what I expect when filtering lists.
I choose the first filter and if necessary I continue to add more if I don't receive the desired results.

  1. give me all german members
  2. only in Hamburg
  3. only male -> desired list ready.

What is happening currently?

  1. Give me all german members
  2. City -> I see 800 City from all over the world, so I can chose Belfast and there are no matches.

In this example it is obvious that it does not match Germany & Belfast.
But there are other attributes where it is not obvious at all.
For example: specific member groups, function in company, active....

The feedbacks from plenty of our customer editors is the the current filtering method is not intuitiv nor logical.
Dependencies would help from my perspective. Technically this would assume to get rid of these tiny Filter Action buttons and use immediate action in the dropdown -> selecting a country would immediately filter the results. -> quicker and more accurate due to less clicks and a reduced select list for the remaining filter options.
Only a reset Button would be necessary at the end (which would better be labeled as "reset filter" after all).

@aschempp aschempp added feature help wanted Issues and PRs which are looking for volunteers to complete them. and removed bug unconfirmed labels Dec 28, 2023
@aschempp
Copy link
Member

Labeling this as feature request, because it certainly is not a bug (even though you might consider it non-optimal.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature help wanted Issues and PRs which are looking for volunteers to complete them.
Projects
None yet
Development

No branches or pull requests

4 participants