-
Notifications
You must be signed in to change notification settings - Fork 14.6k
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
Other admin users can't see "saved queries" created by another admin users #20604
Comments
Hello. Any news? We're trying to track our table references in Superset and this is the only part left. |
This can temporarily solve the problem @emilija-omnisend @winglight
|
I think this should be merged, otherwise the share link functionality is meaningless. |
We are planning to add UUID query lookup support in the near future to fix this problem. There should be a fix in 3.0. |
@eschutho do you know if that work transpired and this was just never closed? |
I'm looking for this solution. I have other users that have Admin Role and they can't see the saved queries. |
To bypass this problem (or unimplemented feature), I did the following:
Done! Now, the other admin will have the same query (query, description, name) saved to their account. This isn’t the best method, as if one admin edits the query, it won’t be updated for others. However, until this feature is implemented, I believe it's a workaround to transfer SQL queries between admins. I hope this function will be implemented someday, as Superset’s ability to transfer/backup dashboards and charts is quite good compared to other open-source BI tools. |
A clear and concise description of what the bug is.
How to reproduce the bug
Expected results
Show the list of all saved queries despite of creators
Actual results
Only queries created by the current user can be shown in the list
Screenshots
Environment
(please complete the following information):
commit 16654034849505109b638fd2a784dfb377238a0e
3.8.12
none
Checklist
Make sure to follow these steps before submitting your issue - thank you!
Additional context
My superset runs on a docker container by docker-compose.
The text was updated successfully, but these errors were encountered: