GitHub user dosubot[bot] added a comment to the discussion: Mixed Timeseries chart does not expose existing X-Axis Sort controls (pip installation)
<!-- Greeting --> Hi @S23-dot! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the superset team. <!-- Answer --> You're investigating the correct area, but the situation is slightly different from what you assumed. The Mixed Timeseries chart **does not** use `echartsTimeSeriesQuery` or `echartsTimeSeriesQueryWithXAxisSort`. Instead, it has its own custom control panel implementation using a `createQuerySection()` helper because it needs to support two independent queries (Query A and Query B) [[1]](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset-frontend/plugins/plugin-chart-echarts/src/MixedTimeseries/controlPanel.tsx#L64-L133). The control panel config file is located at: **`superset-frontend/plugins/plugin-chart-echarts/src/MixedTimeseries/controlPanel.tsx`** [[2]](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset-frontend/plugins/plugin-chart-echarts/src/MixedTimeseries/controlPanel.tsx) For comparison, the regular Timeseries chart variants (Line, Bar, Area, etc.) use `sections.echartsTimeSeriesQueryWithXAxisSort` [[3]](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset-frontend/plugins/plugin-chart-echarts/src/Timeseries/Regular/Line/controlPanel.tsx#L61), which includes the `xAxisSortControl`, `xAxisSortAscControl`, and `xAxisForceCategoricalControl` controls [[4]](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset-frontend/packages/superset-ui-chart-controls/src/sections/echartsTimeSeriesQuery.tsx#L47-L58). These controls are simply **absent** from the Mixed Timeseries custom query sections. So the fix would involve adding those X-axis sort controls into the Mixed Timeseries `controlPanel.tsx`—likely into the shared query fields section or the `createQuerySection()` function—rather than swapping one predefined section for another. You'd need to be mindful of the dual-query architecture when wiring up the sort behavior. In a pip-installed setup, the compiled frontend assets won't be directly editable in a practical way. If you want to make this change, you'd need to work from the source (`superset-frontend/`) and rebuild the frontend, or contribute a PR upstream. <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=reply-with-mention&utm_term=apache%2Fsuperset).* --- Docs are dead. Just use [Dosu](https://dosu.dev?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=static-docs-tagline&utm_term=apache%2Fsuperset). [](https://app.dosu.dev/response-feedback?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=static-docs-feedback&utm_term=apache%2Fsuperset&message_id=90bba9d7-a796-44d8-b4d5-07ecc4a5e4a9) [](https://github.dosu.com/apache/superset?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=static-docs-ask-repo&utm_term=apache%2Fsuperset) [](https://app.dosu.dev/signup?referrer=openSource&source=github-footer&utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=static-docs-share-team&utm_term=apache%2Fsuperset) GitHub link: https://github.com/apache/superset/discussions/40011#discussioncomment-16876015 ---- 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]
