feat(inbox): add "Any" option to Source and Priority filters

[pauldambra]

Problem

In the inbox toolbar, the Source and Priority filter dropdowns had no explicit way to get back to "no filter". Once you picked one or more values, the only way to clear was to manually unselect each one — there was no "Any" affordance, which is unintuitive (raised in the Slack thread linked below).

Changes

• Add an Any row as the first item in both the Source and Priority filter popovers.
• "Any" is shown as selected (check mark) whenever no specific value is selected, and clicking it clears that filter back to empty.
• Unselecting the last remaining option collapses to the same empty state — i.e. it is equivalent to clicking "Any".
• Backed by two small per-filter store actions (clearSourceProductFilter, clearPriorityFilter); empty array still means "all", so no query/serialization changes.

Note: the mobile FilterSheet uses a different paradigm (a sheet with a global "Reset" button), so it's left as-is; we can mirror the per-select "Any" there as a follow-up if desired.

How did you test this?

• pnpm --filter @posthog/ui test inboxSignalsFilterStore — 14 tests pass, including new cases for clearPriorityFilter, clearSourceProductFilter, and "toggling off the last source is equivalent to Any".
• pnpm --filter @posthog/ui typecheck — clean.
• biome lint on the changed files — clean.

Automatic notifications

• Publish to changelog?
• Alert Sales and Marketing teams?

---

Created with PostHog from a Slack thread

[trunk-io]

😎 Merged successfully - details.

[github-actions]

React Doctor found no issues in the changed files. 🎉

_{Reviewed by React Doctor for commit 242da08.}

[pauldambra]

Note

🤖 Automated comment by QA Swarm — not written by a human

Multi-perspective review (paul-reviewer, xp-reviewer, security-audit; qa-team unavailable in this environment). Verdict: ✅ APPROVE WITH NITS — no correctness or security issues, only nit/low suggestions inline.

[pauldambra]

Note

🤖 Automated comment by QA Swarm — not written by a human

Multi-perspective review: paul-reviewer, xp-reviewer, security-audit (qa-team unavailable in this environment)

Verdict: ✅ APPROVE WITH NITS

Small, focused change that does exactly one thing: makes the already-documented "empty = Any" filter state reachable from the UI. No correctness bugs, no security surface, store actions are tested.

Key findings

• 🟢 LOW — clearSourceProductFilter/clearPriorityFilter overlap with resetFilters/setPriorityFilter([]); keep for call-site readability but single-source the "empty = Any" invariant. (convergent: paul + xp)
• 🟢 LOW — no data-attr on the filter buttons; this is a measuring surface, cheap to add now (pre-existing gap, not a regression). (paul)
• ⚪ NIT — InboxFilterAnyItem's label prop is always "Any" — could hardcode. (convergent: paul + xp)
• ⚪ NIT — "Any" row sits flush-left vs icon-indented siblings. (paul)
• ⚪ NIT — the "toggling off the last source" test characterizes pre-existing behavior. (xp)

Convergence

Two findings were flagged independently by both paul and xp (higher confidence): the always-"Any" label prop, and the clear-action / resetFilters overlap.

Reviewer summaries

Reviewer	Assessment
👤 paul	Clean, does one thing; only itch is observability (pre-existing). Ship it.
📐 xp	Well-shaped, no YAGNI violations; nice InboxFilterAnyItem extraction. Ship it.
🛡 security-audit	Security-neutral — no user-controlled data flow, no new auth/injection surface.

---

Automated by QA Swarm — not a human review

[pauldambra]

Merge activity

• Jul 16, 11:58 AM UTC: A user started a stack merge that includes this pull request via Graphite.