Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug: Sorting a breakdown on an unsaved insight deletes the insight #9568

Closed
3 tasks
joethreepwood opened this issue Apr 28, 2022 · 0 comments · Fixed by #11456
Closed
3 tasks

Bug: Sorting a breakdown on an unsaved insight deletes the insight #9568

joethreepwood opened this issue Apr 28, 2022 · 0 comments · Fixed by #11456
Labels
bug Something isn't working right feature/saved-insights Feature Tag: Saved Insights

Comments

@joethreepwood
Copy link
Contributor

joethreepwood commented Apr 28, 2022

Bug description

I was making an insight to look into the locations of users by timezone (though I've repeated this bug with other insights and it happens there too).

Important to clarify that this was on an unsaved insight because I didn't need to save it (and this bug doesn't effect saved insights). But I did want to sort the breakdown table into a different order. Trying to sort the table prompts this message:

Screenshot 2022-04-28 at 11 09 35

Now, my assumption was that this was because it needs to reload the insight. As in, I'll press OK and it will reload the insight with the table sorted the way I wanted. So, I press OK.

Screenshot 2022-04-28 at 11 06 36

Oh shit, that wasn't what I expected! It's not only removed the breakdown on the insight, it's deleted the entire insight.

Though, apparently the sort I applied on Apr 22 is still applied? Hmm.

So, I rebuild the insight, sort again, this time I press cancel. But that gives a different bug!

How to reproduce

  1. Trends insight, unsaved
  2. Add a breakdown
  3. Sort the breakdown, press OK

Environment

  • PostHog Cloud
  • self-hosted PostHog (ClickHouse-based), version/commit: please provide
  • self-hosted PostHog (Postgres-based, legacy), version/commit: please provide

Additional context

Tagging @lottiecoxon and @clarkus as there's a UI element here possibly in terms of making the error text clearer?

Thank you for your bug report – we love squashing them!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working right feature/saved-insights Feature Tag: Saved Insights
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants