PostHog/posthog

group flags that target groups should have default insights that only show `$feature_flag_called` events with groups associated with them

Open

#39,135 opened on Oct 4, 2025

View on GitHub
 (3 comments) (0 reactions) (0 assignees)Python (988 forks)batch import
good first issueteam/feature-flags

Repository metrics

Stars
 (16,704 stars)
PR merge metrics
 (Avg merge 12h 15m) (1,000 merged PRs in 30d)

Description

right now, we create default insights for feature flags, but if a feature flag targets groups, we should tailor that default insight to only show $feature_flag_called events that have groups set on them, since otherwise these events don't really evaluation traffic to this flag (i.e. it can make the rollout percentages seem confusing since the amount of false events (just bc there are no groups) will be way larger than expected)

Folks have been confused about this: https://posthog.slack.com/archives/C075EH38BR8/p1759134575502819

Contributor guide

Research direction
Find where default insights for feature flags are created (likely in the backend). Modify the logic to detect if a flag targets groups: if so, set the insight to filter for $feature flag called events that have groups set.
Tech stack
python
Domain
backend
Issue type
Feature
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.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Python
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65