You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@superset.apache.org by "mfreyre-smo (via GitHub)" <gi...@apache.org> on 2024/01/22 21:56:11 UTC
[I] Export to Import Unintentional Ownership Change [superset]
mfreyre-smo opened a new issue, #26750:
URL: https://github.com/apache/superset/issues/26750
### Bug description
My team and I noticed that if you export a dashboard and import it again (executing an overwrite) that it changes the ownership of the dashboard to include the uploader. This is default behavior and it seemed like a bug. As a work around we were thinking of disabling export/import for certain users but wanted to bring this issue up regardless and solicit other potential solutions. This was brought up in the Superset Slack Channel where it was advised that this be made into a bug report.
- Experienced on Chrome and Firefox
### How to reproduce the bug
1. Find an existing dashboard that another user created (or one that doesn't have an owner)
2. Export the dashboard
3. Import the dashboard
4. Observe that your account is now shown as an owner of the dashboard
Alternative Steps:
1. Create a dashboard
2. Get someone else to export your dashboard
3. Have that person import the dashboard
4. Observe that you and the other person's accounts are now owners of the dashboard
### Screenshots/recordings
_No response_
### Superset version
master / latest-dev
### Python version
3.11
### Node version
16
### Browser
Chrome
### Additional context
_No response_
### Checklist
- [ ] I have searched Superset docs and Slack and didn't find a solution to my problem.
- [ ] 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: notifications-unsubscribe@superset.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [I] [superset]
Posted by "rusackas (via GitHub)" <gi...@apache.org>.
rusackas commented on issue #26750:
URL: https://github.com/apache/superset/issues/26750#issuecomment-1912332135
The PMC is investigating this one, but I'm removing the public report contents for good measure while we sort it out.
--
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: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [I] [superset]
Posted by "rusackas (via GitHub)" <gi...@apache.org>.
rusackas closed issue #26750: <issue removed>
URL: https://github.com/apache/superset/issues/26750
--
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: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org