You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Wrong group names in Table Time Comparison when not showing all columns #37074
Create a Table Chart with multiple metrics and add a Time Comparison. Then try to not show all of the columns, e.g.:
only show % diff
manually de-select some random comparison column
collapse a group
You will see that the groups in the top line go crazy - they are sometimes randomly wrong, and sometimes their alignment does not fit the particular columns below.
Screenshots/recordings
quick reproduction with some dummy table:
the regular table without any customization (everything is fine)
the table after only showing the % diffs
the table after collapsing the first two groups
the table after manually deselecting the #, △ columns for the first two groups
Superset version
master / latest-dev
Python version
I don't know
Node version
I don't know
Browser
Chrome
Additional context
We are using Preset version 4.2.0.25, i don't know which Superset version this ia´s
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.
This is a known issue with Superset's Table Chart when using Time Comparison and hiding columns or collapsing groups: the group headers can become misaligned or display incorrect names. The root cause is that the logic for grouping and rendering headers relies on substring operations and column indices, which can break when only a subset of comparison columns is visible. This leads to the header labels drifting or duplicating, especially when columns are hidden or reordered.
A recent fix (PR #35968) improved header alignment and accessibility by introducing better header ID generation and grouping, but it doesn't fully resolve cases with duplicate metric labels or complex metric/time-shift combinations. There is currently no open issue or PR tracking this specific bug with group headers when not all columns are shown or groups are collapsed. As a workaround, you can try renaming your metrics to ensure unique labels or use custom CSS targeting header IDs to temporarily mitigate the misalignment. For a long-term fix, the grouping and header ID logic in the TableChart and DataTable components needs to be reviewed for uniqueness and correct mapping. If you can provide a minimal reproducible example or more details about your configuration, it could help maintainers debug and address the problem more effectively.
Activity
dosubot commentedon Jan 13, 2026
Hi @silasdoehler! I'm Dosu and I’m helping the superset team.
This is a known issue with Superset's Table Chart when using Time Comparison and hiding columns or collapsing groups: the group headers can become misaligned or display incorrect names. The root cause is that the logic for grouping and rendering headers relies on substring operations and column indices, which can break when only a subset of comparison columns is visible. This leads to the header labels drifting or duplicating, especially when columns are hidden or reordered.
A recent fix (PR #35968) improved header alignment and accessibility by introducing better header ID generation and grouping, but it doesn't fully resolve cases with duplicate metric labels or complex metric/time-shift combinations. There is currently no open issue or PR tracking this specific bug with group headers when not all columns are shown or groups are collapsed. As a workaround, you can try renaming your metrics to ensure unique labels or use custom CSS targeting header IDs to temporarily mitigate the misalignment. For a long-term fix, the grouping and header ID logic in the TableChart and DataTable components needs to be reviewed for uniqueness and correct mapping. If you can provide a minimal reproducible example or more details about your configuration, it could help maintainers debug and address the problem more effectively.
References:
To reply, just mention @dosu.
How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other
fix(table): align group headers correctly when filtering time compari…
fix(table): align group headers correctly when filtering time compari…