Breakdown by attribute property is broken

[buwilliams]

Bug description

Original bug report

Video of problem

• filtering OUT internal users increases the event count
• filtering OUT internal users increases the event count

Expected behavior

• Event counts are correct.

How to reproduce

See video above.

Environment

• PostHog Cloud
• self-hosted PostHog, version/commit: please provide

Additional context

Originated from customer via Slack.

[EDsCODE]

Need help deciding best way to decide which properties to include on breakdown. Currently, when breaking down given a single event, it's clear that it will be most helpful to find the top X values of the breakdown property requested and then give the breakdown of the event on those values. For example, if the event is $pageview and the breakdown property is 'city', we would breakdown across the top 20 cities where $pageviews have been happening.

However, when provided multiple events (for example: $pageviews and $user_signed_up), the top 20 cities for each event could be different. Do we display this as is? Or is there a better way to decide on these values

[EDsCODE]

Will proceed with displaying the top 20 per event as this makes the most sense in displaying relevant numbers

[macobo]

@EDsCODE what's the state here? What needs to be done, is there a WIP branch somewhere, should someone else on the team pick it up?

[EDsCODE]

I think I was about to pick this up but got hung up on a different sprint and then we hopped into funnels mode. It's open for tackling. Mainly just need to make sure breakdown values are correctly determined per event and that this is clear on the UI. Applicable for funnels too

[posthog-bot]

This issue hasn't seen activity in two years! If you want to keep it open, post a comment or remove the stale label – otherwise this will be closed in two weeks.

[posthog-bot]

This issue was closed due to lack of activity. Feel free to reopen if it's still relevant.