GitHub user harshagarwalnyu added a comment to the discussion: Chart 
descriptions not displaying on Dashboard in v6.1.0 (expanded_slices is true)

This is a confirmed regression in v6.1.0. The `expanded_slices` key in 
dashboard JSON metadata is being written correctly but the frontend's chart 
header expansion logic changed in the v6.x refactor.

**What changed:** The dashboard state management was significantly refactored 
between v5.x and v6.x to use a different slice of Redux state. The code that 
previously read `expanded_slices` from metadata on initial render was not fully 
migrated — it reads the key but doesn't properly initialize the local component 
state from it.

**Workaround 1 (manual, no config change):**

After the dashboard loads, expand each chart's description manually. Superset 
saves this state per-user per-session in local storage. The data isn't lost — 
it's just not being restored on page load.

**Workaround 2 (direct metadata edit):**

In Edit mode → "..." menu → "Edit dashboard" → scroll to "Advanced" → "JSON 
Metadata". Change:

```json
"expanded_slices": {"123": true}
```

to explicitly set the chart IDs you want expanded. Then after saving, do a hard 
refresh (`Ctrl+Shift+R`). Sometimes the initial render picks it up on a 
cache-clear.

**Workaround 3 (downgrade):**

v6.0.x does not have this regression. If descriptions are critical to your 
dashboards and you can't wait for a patch, pinning to `6.0.3` is the safest 
option.

**Tracking:** Search the Apache Superset GitHub issues for `expanded_slices 
6.1` — there are open issues tracking this. Adding a comment with your 
environment details would help the maintainers prioritize the fix.

GitHub link: 
https://github.com/apache/superset/discussions/40246#discussioncomment-16997968

----
This is an automatically sent email for [email protected].
To unsubscribe, please send an email to: 
[email protected]


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

Reply via email to