Skip to content

Inviting an existing member to a workspace on NewDot uses the OldDot invite template #40445

@lanitochka17

Description

@lanitochka17

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!


Version Number: 1.4.63-0
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Email or phone of affected tester (no customers): natnael.expensify+3@gmail.com
Issue reported by: Applause - Internal Team

Issue found when executing PR #38023

Action Performed:

  1. Go to workspace settings
  2. Click on 'Members'
  3. Choose a contact that has an existing Expensify account (and that you have access to an email inbox for)
  4. Invite the existing account to the workspace
  5. Go to the email inbox of that account

Expected Result:

  1. Don't send the OldDot template when inviting existing accounts to a workspace on NewDot
  2. Send the welcomeNote in the workspace chat with the email fallback using the same custom subject header as for a newly invited account:

Subject: [First Name] [Last Name] ([email@user.com]) invited you to [workspaceName]
Body:

Actual Result:

The OldDot template for inviting an existing account is used instead

Workaround:

N/A

Platforms:

Which of our officially supported platforms is this issue occurring on?

  • Android: Native
  • Android: mWeb Chrome
  • iOS: Native
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Screenshots/Videos

image

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~01bf2f17a3669228c7
  • Upwork Job ID: 1785359952219054080
  • Last Price Increase: 2024-05-01

Metadata

Metadata

Labels

BugSomething is broken. Auto assigns a BugZero manager.DailyKSv2EngineeringImprovementItem broken or needs improvement.InternalRequires API changes or must be handled by Expensify staffReviewingHas a PR in review

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions