Sort funnel visualisation by value / tie it to the detailed results table · Issue #33723 · PostHog/posthog · GitHub
More Web Proxy on the site http://driver.im/
You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Scenario: Conversion funnel with a breakdown of many (really, a lot of) different e.g. products. We are interested in the top total conversion or converted, dropped of etc. results. Whilst we can sort in the detailed results table, this order does not reflect in the actual visualisation.
Describe the solution you'd like
Ideal scenario: Have an option to sort the visualised value by certain parameters, e.g. conversion so far etc. Tying the detailed results table, which is sortable, to the visualisation would probably make most sense.
Describe alternatives you've considered
Additional context
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]
The text was updated successfully, but these errors were encountered:
Feature request
Is your feature request related to a problem?
Scenario: Conversion funnel with a breakdown of many (really, a lot of) different e.g. products. We are interested in the top total conversion or converted, dropped of etc. results. Whilst we can sort in the detailed results table, this order does not reflect in the actual visualisation.
Describe the solution you'd like
Ideal scenario: Have an option to sort the visualised value by certain parameters, e.g. conversion so far etc. Tying the detailed results table, which is sortable, to the visualisation would probably make most sense.
Describe alternatives you've considered
Additional context
Debug info
The text was updated successfully, but these errors were encountered: