PostHog / PostHog/posthog

Feature request: Dashboard: Show multiple series as columns in tables with breakdown

Open
#21,063 5 comments 8 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement feature/dashboards team/product-analytics
Dominant language
Python
Stars
39.9k
Forks
3.4k
Avg merge
7h 27m
Merged PRs (30d)
222

Description

Is your feature request related to a problem?

This would help containing insights for a specific breakdown within a single table instead of needing one for each series.

Describe the solution you'd like

This could be an option for the table view and instead of showing a "series" column and giving each series it's own row, hiding the "series" column and showing each series as their own column in the same row.

So a breakdown per page could have one row per page with columns "unique users", "total count", "median session duration".

Describe alternatives you've considered

Using multiple reports.

Additional context

Thank you for your feature request – we love each and every one!

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the dashboard table view and the code handling series and breakdown results. Trace how rows and metric columns are assembled, then define the behavior for showing one row per breakdown with each series as a column. Done means the table supports this option without requiring separate reports, with coverage for the stated example metrics.

Written by the indexing model from the issue text.

Assessment

Domain
analytics, frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.