-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
Dashboard filters #3
Comments
An example of where the strategy of filtering on the "client side" won't work: when doing a query with limit on the results. For each filter the top results will be different. |
Related: #140 . |
|
HI arik, I our case, the global filter is taking first chart's filter value even if there are more values in the filter for second chart. So basically it is not doing union. Please suggest |
Thanks for logging that, @indupulikkot. Can you provide a minimal example that we can look at to fix this? |
Iam attaching a screenshot with the issue description. Please review and suggest a fix for this. Our project is already live and this persists as an issue for us. |
@indupulikkot Thanks for attaching a screenshot, and for letting us know that this is potentially urgent for you. The open source version of Redash is a community project and comes with no warranties or support. We'll fix this issue when we can or when it becomes relevant to our customers, but other issues have a higher priority right now. The fastest way for this to be fixed would most likely be for you to suggest a pull request, which would really be great. Let us know if it's something you need help with, and will review the PR and try and help you land it. If you need commercial support for your Redash deployment, you should use the SaaS version. In some cases we might consider engaging in a support contract for an on-premises deployment, but this is discussed on a case-by-case basis. |
@RichardLitt I updated your comment to better reflect the actual situation (saying Redash is mostly volunteer run is not accurate). @indupulikkot FYI. |
I'm closing this, as most of what described here can be achieved with parameters. If there are specific issues with filters or parameters on dashboards, we should open more granular issues. |
Thanks @arikfr! |
May I know why this issue is closed? C ould you please help us to fix this as we do not require parameters. |
* commit '5bad35d409485f450831dcd57a315bd0c067d563': code refactoring forgot to change circleci username in the artifacts url change ci address to my own
Snlbattery 19 filtering logic
* try making multi-filters default to all haven't tested * Update query-result.js * Update query-result.js
show months in 2 digit numbers instead of name
* Parameter feedback - #3 Added in Widgets * Added cypress tests * Making sure widget-level param is selected * Parameter feedback - #4 Added in Dashboard params (#4321) * Parameter feedback - #4 Added in Dashboard params * Added cypress test * Moved to service * Parameter feedback - #5 Unsaved indication (#4322) * Parameter feedback - #5 Unsaved indication * Added ANGULAR_REMOVE_ME * Added cypress test * Fixed percy screenshot * Some code improvements * Parameter input feedback - #6 Better value normalization (#4327)
* Parameter feedback - #2 Client errors in query page * Added cypress test * Fixed percy screenshot * Safer touched change * Parameter feedback - #3 Added in Widgets (#4320) * Parameter feedback - #3 Added in Widgets * Added cypress tests * Making sure widget-level param is selected * Parameter feedback - #4 Added in Dashboard params (#4321) * Parameter feedback - #4 Added in Dashboard params * Added cypress test * Moved to service * Parameter feedback - #5 Unsaved indication (#4322) * Parameter feedback - #5 Unsaved indication * Added ANGULAR_REMOVE_ME * Added cypress test * Fixed percy screenshot * Some code improvements * Parameter input feedback - #6 Better value normalization (#4327)
User should be able to add a filter to the dashboard that will be applied to all the queries of the widgets displayed.
Such filters can be:
TBD: explain about the two possible implementation strategies.
The text was updated successfully, but these errors were encountered: