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

Add CSAT banner for 716 days after having a Plus subscription #5586

Merged
merged 5 commits into from
Feb 4, 2025

Conversation

flozia
Copy link
Collaborator

@flozia flozia commented Feb 3, 2025

References:

Jira: MNTOR-3991

Description

Add a CSAT survey for users after ~24 months of being a Plus subscriber.

How to test

Storybook

  1. CsatSurvey (AutomaticRemoval): /?path=/story/misc-csatsurvey--csat-survey-automatic-removal
  2. Set elapsedTimeInDaysSinceInitialScan >= 716
  3. Click on a response
  4. The follow-up link href should match the pattern: https://survey.alchemer.com/s3/7714663/* https://survey.alchemer.com/s3/8176616/*

Checklist (Definition of Done)

  • Commits in this PR are minimal and have descriptive commit messages.
  • I've added a unit test to test for potential regressions of this bug.
  • Product Owner accepted the User Story (demo of functionality completed) or waived the privilege.
  • All acceptance criteria are met.
  • Jira ticket has been updated (if needed) with suggestions for QA when this PR is deployed to stage.

@flozia flozia self-assigned this Feb 3, 2025
@flozia flozia requested review from Vinnl and codemist February 3, 2025 17:09
Copy link

github-actions bot commented Feb 3, 2025

Copy link
Collaborator

@Vinnl Vinnl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This must have been satisfying, seeing your previous abstractions pan out so nicely.

"very-dissatisfied":
"https://survey.alchemer.com/s3/8176616/edb0c3f18778",
dissatisfied: "https://survey.alchemer.com/s3/8176616/9b6ca1d007a5",
neutral: "https://survey.alchemer.com/s3/8176616/37955cef0c5e",
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Your PR description says this should follow the pattern 7714663, but I'm seeing the value mentioned here: 8176616. I'm assuming that this is correct.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good catch: It is implemented correctly and mentioned wrongly in the PR description — 8176616 is right. I just updated it.

@flozia flozia merged commit 4166eee into main Feb 4, 2025
16 checks passed
@flozia flozia deleted the mntor-3991 branch February 4, 2025 15:30
Copy link

github-actions bot commented Feb 4, 2025

Cleanup completed - database 'blurts-server-pr-5586' destroyed, cloud run service 'blurts-server-pr-5586' destroyed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants