yousoph opened a new issue, #31367:
URL: https://github.com/apache/superset/issues/31367

   ### Bug description
   
   ## Description
   Users are unable to share saved SQL queries to other users. The owner of a 
saved query can access it via the shared URL, but any other user attempting to 
access the same URL receives an error message: “The query couldn’t be loaded."
   
   ## How to reproduce the bug
   1. Log in and save a query in SQL Lab.
   2. Copy the query URL using the "Copy Query URL" option.
   3. Share the URL with a different user.
   4. Have the other user try to load the shared query URL.
   5. Observe that the second user receives the error message: “The query 
couldn’t be loaded.”
   
   ## Expected results
   Any user with access to SQL Lab should be able to load and view saved SQL 
queries via a shared URL.
   
   ## Actual results
   Only the creator of the query can load the query from the shared URL. Other 
users receive an error message stating: "The query couldn’t be loaded."
   
   ### Screenshots/recordings
   
   _No response_
   
   ### Superset version
   
   master / latest-dev
   
   ### Python version
   
   3.9
   
   ### Node version
   
   16
   
   ### Browser
   
   Chrome
   
   ### Additional context
   
   _No response_
   
   ### Checklist
   
   - [X] I have searched Superset docs and Slack and didn't find a solution to 
my problem.
   - [X] I have searched the GitHub issue tracker and didn't find a similar bug 
report.
   - [ ] I have checked Superset's logs for errors and if I found a relevant 
Python stacktrace, I included it here as text in the "additional context" 
section.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to