Mixed timeseries applies the wrong crossfilter value

[GustafHultgren]

Bug description

Cross filters are not applied properly on mixed time series charts. When clicking on a data point, no cross filter display is rendered at the top of the dashboard filter panel, but at the same time other charts in the same dashboard become empty due to a wrong cross filter value being applied. This happens regardless of plot types for the two plots.

I reckon this is because the value for cross filter event handlers need the formatted column displayName and not the raw seriesName to resolve the filter value through the label map.

Steps to reproduce:

1. Create an empty dashboard
2. Add the "Publishers with most titles" chart to the dashboard
3. Create a mixed time series chart using the same dataset "video_game_sales"
4. Click on a data point in the mixed time series chart

Expected:
A cross filter value display should appear in the filter panel. Also the "Publishers with most titles" should have the proper cross filter applied

Actual:
No cross filter value displayed and the "Publishers with most titles" chart becomes empty

Screenshots/recordings

Expected:

Actual:

Superset version

master / latest-dev

Python version

Not applicable

Node version

Not applicable

Browser

Chrome

Additional context

Related to issue #38870

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.

[sadpandajoe]

@dosu has this been validated?

[dosubot]

@sadpandajoe Based on my research, PR #38120 (merged June 18, 2026) addresses a closely related cross-filter issue in EchartsMixedTimeseries.tsx — it fixes incorrect dimension value extraction by calculating a metricsCount offset so cross-filters emit dimension values instead of metric labels [1].

However, the bug reported here appears to be a different but related mismatch: the ECharts click event emits the series displayName (e.g. "metric (Query B), dimension_value"), but the labelMap is keyed by a different format (the raw inverted series name or with a "(1)" suffix for Query B). This means getCrossFilterDataMask does a lookup against currentLabelMap[seriesName] that returns undefined because the key formats don't match [2] [3].

I could not find a PR specifically referencing this issue (#41622) or one submitted by the reporter that addresses this particular displayName-to-labelMap-key mapping problem. So while PR #38120 fixes one dimension of the cross-filter bug (metric vs dimension indexing), the issue described here — where the raw seriesName from ECharts events doesn't match labelMap keys at all — may still be open. I'd recommend verifying on the latest master whether the cross-filter still fails after PR #38120's merge.

To reply, just mention @dosu.

---

Share context across your team and agents. Try Dosu.