-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Inviting an existing member to a workspace on NewDot uses the OldDot invite template #40445
Comments
Triggered auto assignment to @mallenexpensify ( |
@mallenexpensify FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors |
We think that this bug might be related to #wave-collect - Release 1 |
@Gonals could you please take a look at this as per #38023 (comment)? Thank you! |
Good 👀 @rayane-djouah , thanks for tagging and linking. Awaiting feedback from @Gonals |
Hey @lanitochka17 I'm a bit unsure of what you were expecting in that box? Do you mind outlining a bit more information on what you think the issue is. I don't think we changes the contents of the welcomeNote, we just changed the notification/email that we send once it's done. |
@mallenexpensify Whoops! This issue is 2 days overdue. Let's get this updated quick! |
@danielrvidal Hey, according to PR #38023 |
Pinged @Gonals in NewDot for 👀 on this and the PR |
@mallenexpensify Eep! 4 days overdue now. Issues have feelings too... |
@Gonals gonna assign you to help catch your 👀 |
This has been labelled "Needs Reproduction". Follow the steps here: https://stackoverflowteams.com/c/expensify/questions/16989 |
Job added to Upwork: https://www.upwork.com/jobs/~01bf2f17a3669228c7 |
@mallenexpensify @c3024 this issue was created 2 weeks ago. Are we close to a solution? Let's make sure we're treating this as a top priority. Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks! |
@mallenexpensify, @c3024 Eep! 4 days overdue now. Issues have feelings too... |
Waiting for internal pickup. We have site issues and deploy freeze, I'll revisit next week. |
@mallenexpensify, @c3024 Huh... This is 4 days overdue. Who can take care of this? |
Posted in #wave-collect and cross posted in #engineering to try to get a volunteer |
@Gonals back in a few days |
@mallenexpensify, @c3024 Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
Waiting for @Gonals return |
I'm back! |
@mallenexpensify, @trjExpensify, if I'm understanding this correctly, we basically want the same message to be sent for existing accounts and for new accounts, right? |
Yep, that's correct. We want to use the same message for existing and new accounts invited to workspaces in NewDot. 👍 |
@Gonals, @mallenexpensify, @c3024 Whoops! This issue is 2 days overdue. Let's get this updated quick! |
Not overdue. In fact, this should be fixed. Closing |
If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] 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): [email protected]
Issue reported by: Applause - Internal Team
Issue found when executing PR #38023
Action Performed:
Expected Result:
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?
Screenshots/Videos
View all open jobs on GitHub
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: