-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Visualization type is not always respected, when filters are applied #17524
Labels
.Frontend
Priority:P2
Average run of the mill bug
.Reproduced
Issues reproduced in test (usually Cypress)
Type:Bug
Product defects
Visualization/
Projects
Milestone
Comments
flamber
added
Type:Bug
Product defects
Priority:P2
Average run of the mill bug
Visualization/
.Frontend
labels
Aug 20, 2021
nemanjaglumac
added a commit
that referenced
this issue
Aug 24, 2021
…n filters are applied (#17565)
This was referenced Jan 18, 2023
This was referenced Feb 27, 2023
This was referenced Oct 1, 2023
This was referenced Jan 11, 2024
This was referenced Feb 5, 2024
Merged
Open
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
.Frontend
Priority:P2
Average run of the mill bug
.Reproduced
Issues reproduced in test (usually Cypress)
Type:Bug
Product defects
Visualization/
Describe the bug
When a question is saved with a specific visualization type, then applying filters can sometimes change the visualization type.
Reproduce 1
{{num}}
as Number1
into the filter widget - it now changes to Table visualization and the question becomes "dirty" with the Save-button activeReproduce 2
ID > 0
- it now changes to Bar visualization.Looking at the URL hash, it contains
"display":"funnel","displayIsLocked":true
but that's not being respected.Expected behavior
The auto-viz logic can be tricky, but if the column structure of results doesn't change, then the viz selection should be respected.
It should be the sweet spot between lax and aggressive, which historically has been difficult to get correct (see PR #12476)
Information about your Metabase Installation:
Tested 0.40.2
Additional context
Likely very related to #16334
The text was updated successfully, but these errors were encountered: