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

   Our filter_scopes mapping is being removed from the dashboard_properties 
after changing the dashboard slug
   
   Hello! I have encountered a bug for Superset 2.1.0
   
   #### How to reproduce the bug
   
   1. Create new dashboard
   2. Add filter boxes and charts in the created dashboard
   3. Using filter-mapping from the edit menu (top-right, three dots), add 
scope for each filter box that is not the default
   4. Check the Dashboard Properties > Advanced > JSON Metadata:  the filter 
mapping updates the dashboard properties through the filter_scopes key. It 
exists in this step since the filter mapping is modified.
   5. Go back to the Superset dashboard lists > Edit Dashboard and replace the 
slug
   6. Go to the Dashboard > Edit Dashboard > Edit Dashboard Properties > 
Advanced
   7. See the JSON Metadata
   
   ### Expected results
   
   The `filter_scopes` key is still there.
   
   ### Actual results
   
   The `filter_scopes` key is no longer there.
   
   ### Environment
   
   (please complete the following information):
   
   - browser type and version: Microsoft Edge Version 115.0.1901.183 (Official 
build) (64-bit)
   - superset version: Apache Superset 2.1.0
   - python version: Python 3.9
   - node.js version: `node -v`
   - any feature flags active: cross-filter enabled, VERSIONED_EXPORT enabled
   
   ### Checklist
   
   Make sure to follow these steps before submitting your issue - thank you!
   
   - [v] I have checked the superset logs for python stacktraces and included 
it here as text if there are any.
   - [v] I have reproduced the issue with at least the latest released version 
of superset.
   - [v] I have checked the issue tracker for the same issue and I haven't 
found one similar.
   
   ### Additional context
   
   Add any other context about the problem here.
   


-- 
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