PostHog / PostHog/posthog

Bug: Breakdown value conflict

Open
#46,804 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug team/product-analytics
Dominant language
Python
Stars
39.9k
Forks
3.4k
Avg merge
6h 51m
Merged PRs (30d)
232

Description

Bug Description

Bug description

Please describe.
Users cant run a breakdown by an event property named value. The root cause looks to be in posthog/queries/breakdown_props.py:303, where every breakdown expression is aliased as unquoted AS value.

How to reproduce

  1. Send an event with a property named value
  2. Go to Insights and create a Trends query for that event
  3. Add a breakdown by the event property value
  4. query fails

Additional context

From: https://posthoghelp.zendesk.com/agent/tickets/49300 (moved to PostHog: https://us.posthog.com/project/2/support/tickets/51519)

Debug info
null

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 in posthog/queries/breakdown_props.py at line 303 and reproduce the failure by creating a Trends query with a breakdown on an event property named value. Confirm the breakdown query no longer fails for that property and check that ordinary breakdowns still work.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
analytics, backend
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.