PostHog / PostHog/posthog

Shared metrics list only shows 100 metrics, hides the rest

Open
#44,543 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Bug Description

The shared metrics list under Experiments will only show 100 metrics, any beyond that get hidden. A customer wrote in about the list not showing all items (https://posthoghelp.zendesk.com/agent/tickets/46489 (moved to PostHog: https://us.posthog.com/project/2/support/tickets/49401)) and I've recreated it on a personal account which can be seen (user 238862 in admin, US region, Default project).

How to reproduce

  1. Create 101 shared metrics
  2. Note you can't see all of them (I numbered mine 1-110, 90-99 are missing in the list due to sort order)

Additional context

Might also be worth adding a search field on this page, as a user with that many shared metrics might find value in being able to search for them as well.

Debug info
- [ ] PostHog Cloud, Debug information: [please copy/paste from https://us.posthog.com/settings/project-details#variables or https://eu.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

Start at the shared metrics list under Experiments and reproduce the issue by creating 101 shared metrics, as described. Trace how the list is loaded and sorted, then verify that all metrics are visible and that the result remains usable for larger lists; search is additional context rather than a required outcome.

Written by the indexing model from the issue text.

Assessment

Tech stack
python, react
Domain
analytics, frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.