PostHog/posthog

Bug: SQL insights visualization customization copies current Y-axis settings to previous item

Open

#30932 opened on Apr 8, 2025

View on GitHub
 (3 comments) (0 reactions) (0 assignees)Python (16,704 stars) (988 forks)batch import
bugfeature/insightsfeature/sql-editorgood first issueteam/product-analytics

Description

Bug Description

Bug description

This is happening intermittently so it's tricky to reproduce. Here's a loom showing the issue: https://www.loom.com/share/6e9a698f4aee4842844a22e0c08451e3

How to reproduce

  1. In the SQL editor, add multiple Y axes
  2. Customize the visualization for each Y axis, including editing the display name
  3. Starting with the second visualization, editing it will copy its settings to the previous one

Additional context

From: https://posthoghelp.zendesk.com/agent/tickets/28511

Debug info

Session: https://us.posthog.com/project/sTMFPsFhdP1Ssg/replay/0196156e-63af-7f6b-a402-50ac26468534?t=0
Admin: http://go/adminOrgUS/018d351a-9ff7-0000-eaff-4628875ad045 (project ID 50689)
Sentry: http://go/sentryUS/50689
Location: https://us.posthog.com/project/50689/sql

Contributor guide

Tech stack
reacttypescriptnodejs
Domain
frontend
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
needs investigation
Prerequisites
ReactTypeScriptFamiliarity with PostHog productDebugging intermittent issues
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
25
Research direction
Investigate the SQL insights visualization component (likely under frontend/src/scenes/sql or similar). The bug occurs when customizing multiple Y axes; the second customization overwrites the first. Watch the Loom video for reproduction steps. Look at how Y axis settings are stored in state (maybe Redux or React context) and how the customization UI updates the state. Check if there's a missing uniqueness key or improper state merging. Review the component's event handlers and ensure each axis's settings are independently managed.