group flags that target groups should have default insights that only show `$feature_flag_called` events with groups associated with them · PostHog/posthog#39135

(3 comments) (0 reactions) (0 assignees)Python (16,704 stars) (988 forks)batch import

good first issueteam/feature-flags

説明

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

コントリビューターガイド

技術スタック: pythonpostgresql
領域: backendanalytics
Issue 種別: feature
難度: 3
推定時間: 1-2 days
活動状況: fresh
明確さ: mostly clear
前提条件: Understanding of PostHog feature flagsFamiliarity with default insights creationKnowledge of event properties filtering
初心者向け度: 50
調査方針: The issue is to modify the default insight creation for feature flags that target groups. Look into how default insights are generated for feature flags (likely in plugin or insight creation code) and add a filter to only include $feature flag called events that have a 'groups' property. The Slack thread referenced (C075EH38BR8) may contain further details. Check the feature flag model and the default insight generation logic.