PostHog / PostHog/posthog

Feature Request: Add at-a-glance indicators for experiment metrics

Open
#102,461 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement feature team/experiments
Dominant language
Python
Stars
39.9k
Forks
3.4k
Avg merge
6h 51m
Merged PRs (30d)
232

Description

Feature request

Is your feature request related to a problem?

  • You can only see if an experiment is working by opening them up and looking at the individual metrics.
  • You can run multiple experiments at the same time.
  • This means in order to see the status of each experiment, you'll have to open up each one and look them over.
  • This becomes cumbersome if you have a lot of experiments going on, and you want to get a gut feeling if any of them are not succeeding.

Describe the solution you'd like

  • It would be great to have a visual success indicator next to an experiment.
  • Perhaps, something akin to a column showing the primary metrics in a red/yellow/green status indicator.
  • Ideally, you can hover over that indicator to see the current status of the metric.
  • Something like this:
Image

Describe alternatives you've considered

  • You could have the AI summarize them, or potentially create some insights.

Additional context

From https://us.posthog.com/project/2/support/tickets/74318

Debug info
- [ X] PostHog Cloud, region and project ID: [please provide, you can find both at https://app.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

No files or tests are named. Start by locating the experiment overview and the existing primary-metric display, then determine where experiment status is assembled. Done should include an at-a-glance indicator for each experiment, hoverable metric status details, and coverage for the displayed states.

Written by the indexing model from the issue text.

Assessment

Tech stack
react, typescript
Domain
analytics, frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.