Filters are not applied to charts after navigating away from and returning to a dashboard that contains multiple tabs.
- Dominant language
- Python
- Stars
- 74.8k
- Forks
- 18.3k
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 685
Description
### Bug description
When a dashboard contains multiple tabs, applied filters are not correctly reflected in the charts after navigating away from the dashboard and then returning to it.
**Steps to Reproduce**
- Open a dashboard that contains multiple tabs.
- Apply one or more dashboard filters.
- Verify that the charts are updated based on the selected filter values.
- Navigate to another page (for example, another dashboard, chart, or any other application page).
- Return to the original dashboard.
**Actual Behavior**
The previously applied filters remain visible in the filter state; however, the charts do not consistently reflect the applied filter values after returning to the dashboard.
**Expected Behavior**
The dashboard should preserve and correctly apply the selected filter values to all charts when the user navigates away from the dashboard and returns to it.
### Screenshots/recordings
https://github.com/user-attachments/assets/f2be83ce-1c4b-4de9-baa6-e34ecf7e68d2
### Superset version
6.0.0
### Python version
3.11
### Node version
18 or greater
### 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.
Contributor guide
Research direction
Reproduce the issue using a dashboard with multiple tabs, applying filters before navigating away and returning. Start at the dashboard filter and chart state restoration flow, then verify that the selected values are applied consistently to every chart after return; done means the visible filter state and chart results remain aligned.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, react
- Domain
- data-visualization, frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100