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

Cannot filter only on longitude/latitude range - UX is forcing user to fill out values for both fields #16291

Closed
nemanjaglumac opened this issue May 31, 2021 · 1 comment
Assignees
Labels
Priority:P3 Cosmetic bugs, minor bugs with a clear workaround Type:UX Visualization/Maps
Milestone

Comments

@nemanjaglumac
Copy link
Member

Describe the bug
The UX around filtering inside longitude or latitude is quite illogical in that it forces you to use both columns to be able to add filter.

Logs
N/A

To Reproduce
Steps to reproduce the behavior:

  1. New custom question > Sample Dataset > People
  2. Click on the Longitude header cell
  3. Click on "Filter by this column
  4. Choose inside type of filter
  5. You will be presented with the four filters in total (upper/lower latitude, left/right longitude)
  6. Without filling out all four fields, it is impossible to add filter

Expected behavior
Show only the related filter values.

Screenshots
image

Information about your Metabase Installation:
local dev > release 39, H2, Sample Dataset

Severity
P3, UX

@nemanjaglumac nemanjaglumac changed the title Cannot filter only on longitude/latitude - UX is forcing user to fill out values for both fields Cannot filter only on longitude/latitude range - UX is forcing user to fill out values for both fields May 31, 2021
@flamber flamber added Priority:P3 Cosmetic bugs, minor bugs with a clear workaround Visualization/Maps and removed .Needs Triage Type:Bug Product defects labels May 31, 2021
@flamber
Copy link
Contributor

flamber commented May 31, 2021

I think the "Inside" operator is correct, but perhaps we should include others like "Between", "Greater than", etc.
Workaround is to use Custom Expression

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Priority:P3 Cosmetic bugs, minor bugs with a clear workaround Type:UX Visualization/Maps
Projects
None yet
Development

No branches or pull requests

3 participants