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

Leaving users survey improvements #6755

Closed
28 tasks done
Pa7Hub opened this issue Mar 20, 2024 · 0 comments · Fixed by #6920
Closed
28 tasks done

Leaving users survey improvements #6755

Pa7Hub opened this issue Mar 20, 2024 · 0 comments · Fixed by #6920
Labels
improvement nice-to-haves that are not impeding usage of any features state:tested We tested it and are about to release it
Milestone

Comments

@Pa7Hub
Copy link
Contributor

Pa7Hub commented Mar 20, 2024

As provider of Tuta we want to not only gather information about why users are leaving, but have selection options in the dropdowns for specific reasons that allow us to react in more detail later.

See server issue tutadb#1791 for more information

AC

  • app.tuta.com/termination offers a button that opens the SurveyWizard
  • app.tuta.com/termination can be completed without taking part in the survey
  • Dropdown and large textfield has new styling
    • Helplabel is rendered properly
    • Editor no longer grows with too many lines, but becomes scrollable instead
    • Editor only uses 1 line when in mobile view
    • Editor uses 5 lines when in desktop view
  • Global Settings > Delete Account will prompt the user with the SurveyWizard
    • Skipping or completing the survey will open the 'Delete' dialog
  • Plan > Downgrade to free will prompt the user with the SurveyWizard
    • Skipping or completing the survey will open the downgrade confirmation dialog
  • SurveyWizard consists of two steps
  • First step: button can only be pressed if value has been selected in dropdown
  • Second step: button can only be pressed if value has been selected in dropdown
  • Second step: picture and header text is related to what has been selected on first step
  • First step: when arriving from 'delete account' in the first dropdown, price category is not available if the account is a free account (Does not apply to termination or downgrade)
  • First step: information text changes depending on whether it's a downgrade or deletion
  • Dialog looks the same on mobile and tablet devices
  • Navigating to the next wizard step will scroll the contents to the top (most visible on mobile)
  • Results can be downloaded from the admin client
  • Old results can no longer be exported
  • The values in the csv correspond to the selectable values in the client
    • 'version' is '0' for all entries
  • Escaping in csv works fine when user enters ",; in the 'Details' section

Test notes

  • All AC are met
  • Regression testing: Termination, Delete, Downgrade
  • Regression testing: Onboarding wizard style looks good
  • Deleting account with old client works fine
@Pa7Hub Pa7Hub added the bug broken functionality, usability problems, unexpected errors label Mar 20, 2024
@Pa7Hub Pa7Hub self-assigned this Mar 20, 2024
@Pa7Hub Pa7Hub added improvement nice-to-haves that are not impeding usage of any features and removed bug broken functionality, usability problems, unexpected errors labels Mar 20, 2024
armhub pushed a commit that referenced this issue May 7, 2024
@armhub armhub linked a pull request May 7, 2024 that will close this issue
armhub pushed a commit that referenced this issue May 7, 2024
github-merge-queue bot pushed a commit that referenced this issue May 7, 2024
Co-authored-by: pas <pas@tutao.de>
@armhub armhub added this to the 228.240506 milestone May 7, 2024
@armhub armhub added the state:tested We tested it and are about to release it label May 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
improvement nice-to-haves that are not impeding usage of any features state:tested We tested it and are about to release it
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants