-
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
Adding filter of summarized field grouped by latitude and longitude on a map changes visualization type #32075
Labels
.Frontend
Priority:P2
Average run of the mill bug
.Reproduced
Issues reproduced in test (usually Cypress)
Type:Bug
Product defects
Visualization/Maps
Milestone
Comments
kamilmielnik
added
Type:Bug
Product defects
.Needs Triage
.Team/42 🌌
.Frontend
Visualization/Maps
labels
Jul 3, 2023
kamilmielnik
added
Priority:P2
Average run of the mill bug
and removed
.Needs Triage
labels
Jul 3, 2023
This was referenced Aug 2, 2023
Closed
This was referenced Aug 18, 2023
QP: use MLv2 metadata provider. Eliminate 50% of app DB calls and improve performance by 10%+
#33221
Merged
This was referenced Jan 11, 2024
This was referenced Feb 5, 2024
Closed
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/Maps
Originally reported in #30057 (there were 2 issues reported there, extracting one here). Other issues with the same reproduction scenario: #30056, #30058
Describe the bug
Filtering on aggregate column after binning on a map changes visualization type
To Reproduce
Steps to reproduce the behavior (if you can reproduce the bug using the Sample Database, we will find the issue faster):
Expected behavior
Expect visualization type not to change to table. It should still be a map.
Logs
No response
Information about your Metabase installation
Metabase version: 45.3.1, 46.1, and master (as of 2023-04-12, still there as of 2023-07-03)
Severity
The text was updated successfully, but these errors were encountered: