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

Have custom domain always be first when adding email address #6890

Closed
5 tasks done
wrdhub opened this issue Apr 26, 2024 · 0 comments · Fixed by #6892
Closed
5 tasks done

Have custom domain always be first when adding email address #6890

wrdhub opened this issue Apr 26, 2024 · 0 comments · Fixed by #6892
Labels
bug broken functionality, usability problems, unexpected errors state:done meets our definition of done state:tested We tested it and are about to release it
Milestone

Comments

@wrdhub
Copy link
Contributor

wrdhub commented Apr 26, 2024

Currently, there are some cases when tuta.com is the default address domain when adding addition email addresses instead of the custom domain. If there is a custom domain, it should always be the default.

Test notes

  • free account cannot add extra email addresses
  • paid account can add extra email addresses, has tuta.com as the default domain
  • paid account with custom domain can add extra email addresses, has the custom domain as the default domain
  • legacy paid account can add extra email addresses, has tutamail.com as the default domain
  • legacy paid account with custom domain can add extra email addresses, has the custom domain as the default domain
@wrdhub wrdhub added bug broken functionality, usability problems, unexpected errors desktop Desktop client related issues labels Apr 26, 2024
@wrdhub wrdhub self-assigned this Apr 26, 2024
@kib42 kib42 removed the desktop Desktop client related issues label Apr 26, 2024
@murilopereirame murilopereirame added the state:done meets our definition of done label May 14, 2024
@kib42 kib42 added this to the Notifications milestone May 21, 2024
@wrdhub wrdhub removed their assignment May 22, 2024
@rezbyte rezbyte assigned rezbyte and unassigned rezbyte May 24, 2024
@charlag charlag self-assigned this May 27, 2024
@charlag charlag added the state:tested We tested it and are about to release it label May 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug broken functionality, usability problems, unexpected errors state:done meets our definition of done state:tested We tested it and are about to release it
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants