PostHog / PostHog/posthog

ephemeral collections in replay

Open
#36,966 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Python
Stars
39.9k
Forks
3.4k
Avg merge
7h 27m
Merged PRs (30d)
222

Description

Feature request

there are a number of places where it would be cool to have an easily embeddable / displayable collection of recordings from a known list of session ids

currently we have

  • saved filters -> the user knows conditions they want to come back to, but we don't know what recordings will show
  • collections -> fixed set of sessions the user added to a collection
  • ephemeral collection -> a known set of session ids that we want to put in place that we generate (not the user)

they're ephemeral to the user since we wouldn't show them in the collections page, so they can only get to them by repeating the flow that got them to the list

example use-case

  • user viewing history to show which recordings they've watched
  • insight datapoints instead of / alongside the actor modal, jump from a funnel drop-off to a list of recordings to watch
  • in notebooks when showing user painpoints in a session summary

since these may be displayed outside of the recording context we probably also want a "mini playlist" experience

Image
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

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no files, tests, or entry points; begin by locating the existing saved-filter and collection flows, then trace how recording session IDs are represented and displayed. Clarify the ephemeral collection lifecycle, the external entry points, and the scope of the proposed mini-playlist before implementation; done should cover the agreed use cases without exposing these collections on the collections page.

Written by the indexing model from the issue text.

Assessment

Domain
full-stack
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.