(surveys) upgrading during survey creation does NOT save your changes
Open
Nobody has claimed this yet.
bug
feature/surveys
- Dominant language
- Python
- Stars
- 39.9k
- Forks
- 3.4k
- Avg merge
- 7h 27m
- Merged PRs (30d)
- 222
Description
Bug Description
bug report
mid-survey-creation, clicking "upgrade" to enable customization features does not auto-save your work before redirecting to stripe
this is a poor CX
How to reproduce
- create a survey in a free-plan account
- do some work on it
- click "upgrade"
- get redirected to surveys -> your work is lost
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
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the survey creation flow and trace the Upgrade action through the redirect to Stripe and back to Surveys. Reproduce the free-plan case while editing a survey, then verify that the in-progress changes remain available after returning from the upgrade flow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, react, typescript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100