Continuing the discussion from Dashboard Fadeout in 0.24 :
Sorry all… figured out what was going on. Fadeout applies to all questions that filter does not apply to. Bit of an odd way of doing things but i think i can group the cards into different dashboards
maz
May 12, 2017, 5:48pm
2
Yeah, this particular UX seems to continue to confound people. If you'd like to add your thoughts, this issue is where we're discussing this:
opened 01:50PM - 24 Jan 17 UTC
closed 04:01PM - 11 Mar 20 UTC
Type:UX
Reporting/Dashboards
Currently when you apply a filter to a dashboard it will fade out all cards that… are not affected by that filter. I understand this behavior is about usability, so users can easily distinguish what data is being affected by the filter they applied. However, if you happen to have more than one filter and apply them all at once, the end result is that all cards get faded and the dashboard becomes hard to read.
As an example, I have the following dashboard where initially users set the Company ID filter. This fills the data for 3 cards and fades out the bottom left one (Prize Winners):
![filter1](https://cloud.githubusercontent.com/assets/1395838/22249492/51da6132-e22a-11e6-8c98-d11b97dd9cfd.png)
If users want more detail, they can pick the "ID" number from the top left card and insert it into the "Prize ID" filter. This fills the data for the bottom left card, but at the same time fades out the other 3 cards... resulting in a totally faded dashboard that is hard to read:
![filter2](https://cloud.githubusercontent.com/assets/1395838/22249555/a88454de-e22a-11e6-8c8a-a01ec6c1c8e6.png)
Maybe the frontend could not fade everything when more than 1 filter is applied?
I'm using 0.22 now but have been experiencing this since filters were introduced in an older release.
Browser: Chrome 55.0.2883.95 (64-bit)
OS: OS X El Capitan (10.11)
Database: MySQL 5.5
Metabase: 0.22
Hosting: Amazon Linux (runs inside my EC2 instance on AWS)
Internal DB: H2
Thanks!