Bug: Insight card view is broken

Open
#39,703 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
react
Domain
analytics, frontend

Research direction

Start at the product analytics entry point and reproduce the transition from list view to card view, then the back-navigation case. Trace why the graphs display the no-matching-events message until refresh; done means both transitions render the graphs correctly without a page refresh.

Written by the indexing model from the issue text.

Description

bug team/product-analytics ui
Bug Description

Please describe.
Graphs in product analyitics Card view do not render until a page refresh upon moving between list and card view. Similarly when clicking into an insight and navigating back to the previous page.

Graphs will show:

There are no matching events for this query
Try changing the date range, or pick another action, event or breakdown.

How to reproduce

  1. Navigate to product analytics
  2. change from list view to card view
  3. graphs show message above

Additional context

https://posthoghelp.zendesk.com/agent/tickets/39651 (moved to PostHog: https://us.posthog.com/project/2/support/tickets/41621)

Debug info
- [ ] PostHog Cloud, Debug information: [please copy/paste from https://us.posthog.com/settings/project-details#variables or https://eu.posthog.com/settings/project-details#variables]
- [ ] PostHog Hobby self-hosted with `docker compose`, version/commit: [please provide]
- [ ] PostHog self-hosted with Kubernetes (deprecated, see [`Sunsetting Kubernetes support`](https://posthog.com/blog/sunsetting-helm-support-posthog)), version/commit: [please provide]
Dominant language
Python
Stars
39.9k
Forks
3.4k
Avg merge
7h 27m
Merged PRs (30d)
222

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.

More from PostHog/posthog

All issues in PostHog/posthog

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.