-
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
FK fields shows sub-dimension selector #16787
Labels
Priority:P3
Cosmetic bugs, minor bugs with a clear workaround
Querying/Notebook
Items specific to the Custom/Notebook query builder
.Regression
Bugs that were previously fixed and/or bugs unintentionally shipped with new features.
Type:UX
Milestone
Comments
flamber
added
Type:UX
Priority:P3
Cosmetic bugs, minor bugs with a clear workaround
Querying/Notebook
Items specific to the Custom/Notebook query builder
.Regression
Bugs that were previously fixed and/or bugs unintentionally shipped with new features.
labels
Jun 27, 2021
pawit-metabase
added a commit
that referenced
this issue
Sep 7, 2021
pawit-metabase
added a commit
that referenced
this issue
Sep 8, 2021
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
Priority:P3
Cosmetic bugs, minor bugs with a clear workaround
Querying/Notebook
Items specific to the Custom/Notebook query builder
.Regression
Bugs that were previously fixed and/or bugs unintentionally shipped with new features.
Type:UX
Describe the bug
FK fields shows sub-dimension selector in Notebook dimension selector. Regression since 0.39.0
To Reproduce
Expected behavior
Don't show the sub-selector, since it's the same as the collapsed parts of the Select.
And we don't have any tests for these, so either remove the sub-select or add tests to prevent any problems.
Information about your Metabase Installation:
Tested 0.38.4 thru 0.39.4 and master
c040f15
(2021-06-25). Regression since 0.39.0The text was updated successfully, but these errors were encountered: