PostHog/posthog

Bug: In Cohorts, the 'set' operator filters in null values for person properties

Open

#29 916 ouverte le 13 mars 2025

Voir sur GitHub
 (4 commentaires) (0 réactions) (0 assignés)Python (988 forks)batch import
bugfeature/cohortsgood first issueteam/feature-flags

Métriques du dépôt

Stars
 (16 704 stars)
Métriques de merge PR
 (Merge moyen 17h 29m) (995 PRs mergées en 30 j)

Description

Bug description

In Cohorts, 'set' operator filters in null values for person properties.

Expected outcome

  • 'set' should filter out null values
  • 'not set' should include null values

Using Have the property vs Does not have the property doesn't solve this because we want to filter out users who have the property but with a null value.

In filters, 'not set' filters in 'null while 'set' filters it out. This means there's an inconsistency with how we handle this in Cohorts.

How to reproduce

  1. Create a cohort and filter by having a person property that you know some users have null for and select 'set'
  2. notice the list of users includes users with 'null'

You can test with this cohort: https://us.posthog.com/project/53137/cohorts/122367

Additional context

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

Debug info

null

Guide contributeur