PostHog / PostHog/posthog

Add folder organization and bulk actions for Experiments

Open
#50,182 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
6h 51m
Merged PRs (30d)
232

Description

Feature request

It would be very useful to have the ability to organize experiments into folders within the Experiments section.

Currently, all experiments appear in a single list, which can become difficult to manage as the number of experiments grows. This is especially challenging when running experiments across multiple countries, markets, or campaign types.

Proposed functionality

1. Create folders for experiments
  • Users should be able to create folders and move experiments into them.

  • Example use cases:

  • Organizing experiments by country (e.g., US, UK, DE).

  • Organizing experiments by campaign type (e.g., onboarding, pricing, retention).

2. Rename folders
  • After a folder is created, it should be possible to rename it at any time.
3. Bulk actions inside folders
  • When viewing experiments within a folder, users should be able to select multiple experiments via checkboxes.

  • This would allow bulk actions such as:
  • Stop experiment

  • Pause experiment

  • Archive experiment

  • Delete experiment

Problem this solves

When all experiments exist in a single list it becomes difficult to manage and navigate them especially when running experiments for multiple regions or initiatives simultaneously. Folder organization would make the experiment list much easier to maintain and scale.

Expected benefit

Adding folder organization and bulk actions would significantly improve experiment management, reduce operational friction and help teams running many experiments stay organized.

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

No files, tests, or entry points are identified in the issue. Start by locating the Experiments section and its experiment list, then define the folder lifecycle, experiment moves, selection behavior, and supported bulk actions before identifying verification coverage.

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.