-
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
"Save" button shouldn't appear before one selects the source for a native question #18148
Labels
.Frontend
Priority:P3
Cosmetic bugs, minor bugs with a clear workaround
Querying/Native
The SQL/native query editor
.Reproduced
Issues reproduced in test (usually Cypress)
Type:Bug
Product defects
Milestone
Comments
flamber
added
.Frontend
Priority:P3
Cosmetic bugs, minor bugs with a clear workaround
Querying/Native
The SQL/native query editor
and removed
.Needs Triage
labels
Sep 30, 2021
Friends with #15946 (comment). |
nemanjaglumac
added a commit
that referenced
this issue
Oct 6, 2021
…ource for a native question (#18259)
This was referenced Jan 11, 2024
This was referenced Mar 26, 2024
Merged
This was referenced Apr 3, 2024
This was referenced Apr 18, 2024
This was referenced Apr 29, 2024
Merged
This was referenced May 8, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
.Frontend
Priority:P3
Cosmetic bugs, minor bugs with a clear workaround
Querying/Native
The SQL/native query editor
.Reproduced
Issues reproduced in test (usually Cypress)
Type:Bug
Product defects
Describe the bug
Metabase currently displays the option to save a native question even before the source (db) for it is selected.
Logs
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The original "Save" button shouldn't even appear before it's actually possible to save the question
Screenshots
Information about your Metabase Installation:
You can get this information by going to Admin -> Troubleshooting.
local dev,
master
, 538a5e6, H2, Sample datasetSeverity
Although annoying, it's a cosmetic one and the backend handles this. P3.
The text was updated successfully, but these errors were encountered: