Feature Request: Retention - Enable row selection in the cohort table
Open
Nobody has claimed this yet.
enhancement
feature/retention
team/product-analytics
- Dominant language
- Python
- Stars
- 39.9k
- Forks
- 3.4k
- Avg merge
- 7h 27m
- Merged PRs (30d)
- 222
Description
Feature request
Is your feature request related to a problem?
Make the rows selectable independently in the table and only the rows selected are displayed on the graph above. Comparing a bunch of Mondays over the last 30 days will show only a few lines, which are easy to read and digest
Additional context
https://posthoghelp.zendesk.com/agent/tickets/39026 (moved to PostHog: https://us.posthog.com/project/2/support/tickets/40884)
Debug info
- [ ] PostHog Cloud, Debug information: [please copy/paste from https://us.posthog.com/settings/project-details#variables]
- [ ] PostHog Hobby self-hosted with `docker compose`, version/commit: [please provide]
- [ ] PostHog self-hosted with Kubernetes (deprecated, see [`Sunsetting Kubernetes support`](https://posthog.com/blog/sunsetting-helm-support-posthog)), version/commit: [please provide]
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by locating the retention cohort table and its graph in the frontend, then verify that selecting rows limits the graph to those cohorts; compare multiple Mondays over 30 days to confirm the result.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react, typescript
- Domain
- analytics, frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100