PostHog / PostHog/posthog

Bug: New Person save/update filter view doesn't respect operator

Open
#51,174 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Bug Description

Bug description

When saving a person filter view, the operator does not seem to be respected for filtering on event, all other event and person properties are respected.

Here I've applied the filter for regex matches Event ~ page, i see related $pageviewand $pageleave events.
Image

However, when I now save this view the filter Event ~ page effectively becomes Event = page as it moves to the top-level built in event filter (resulting in 0 events found)
Image

The same bug behaviour does not seem to exsist for other person or event properties.
Image

How to reproduce

  1. Go to Person table, select a person
  2. Select events
  3. Add a filter (regex matches) for Event where the search term is partial (e.g. page to find $pageviewand $pageleave events)
  4. Some events should show
  5. Now save the view (new or update), you should now see the events dissapear

Additional context

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

Debug info
Kind: bug

Target area: analytics

Report event: http://go/ticketByUUID/386416eb-1f7c-41b6-bfff-936ff0c964c6

Session: https://us.posthog.com/project/sTMFPsFhdP1Ssg/replay/019cdf38-41c2-7381-9ba8-9e7469aaf107?t=58318

Exceptions: https://us.posthog.com/project/2/error_tracking?filterGroup=%7B%22type%22%3A%22AND%22%2C%22values%22%3A%5B%7B%22type%22%3A%22AND%22%2C%22values%22%3A%5B%7B%22key%22%3A%22%24session_id%22%2C%22value%22%3A%5B%22019cdf38-41c2-7381-9ba8-9e7469aaf107%22%5D%2C%22operator%22%3A%22exact%22%2C%22type%22%3A%22event%22%7D%5D%7D%5D%7D

Location: https://us.posthog.com/project/240542/dashboard/622907

Persons-on-events mode for project: person_id_override_properties_on_events

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 from the Person table's event filter and the save/update view flow described in the reproduction steps. Reproduce the regex filter Event ~ page before and after saving, then trace where the operator is transferred; done means the saved view preserves regex matching and still shows matching events.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.