-
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
[HOLD for payment 2024-06-05] [$250] Merge account - Email for merged account is prefixed with 0@ in archived workspace chat #40977
Comments
Triggered auto assignment to @sakluger ( |
We think that this bug might be related to #vip-vsb |
@sakluger 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. |
@sakluger Huh... This is 4 days overdue. Who can take care of this? |
I wonder if we're looking for the account ID instead of the account email. When merging accounts, both accounts end up under a single account ID. That means that if you try referencing the account ID for the account that was merged into the current one, you won't find it. |
Job added to Upwork: https://www.upwork.com/jobs/~01e83a7aa224f88987 |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @getusha ( |
Waiting for proposals. |
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
Waiting for proposals. |
Still waiting for proposals. |
The PR has been opened. |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.76-7 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue: If no regressions arise, payment will be issued on 2024-06-05. 🎊 For reference, here are some details about the assignees on this issue:
|
BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:
|
@trjExpensify thanks for helping while I was out! I'm back and have unassigned you. @getusha could you please complete the BZ checklist and accept the Upwork offer? |
BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:
|
@sakluger could we hold the payment here? i am working on moving payments to ND |
@getusha is that being tracked anywhere? Do you know how much longer until you are moved to NewDot payments? |
Thanks for linking! I'm going to set this issue as a weekly. Could you please leave a comment here when you're ready to accept payment via NewDot? |
Still on hold. |
Hey @getusha - any updates here, or are you still waiting to get set up on NewDot payments? |
Can I get a payment summary so that I can approve for @getusha |
$250 approved for @getusha |
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.65-5
Reproducible in staging?: y
Reproducible in production?: y
Issue reported by: Applause - Internal Team
Action Performed:
Expected Result:
User A email will be displayed correctly in the archived workspace chat.
Actual Result:
User A email is prefixed with 0@ in the archived workspace chat.
Workaround:
n/a
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
Bug6461468_1714043719861.bandicam_2024-04-25_19-08-56-249.mp4
View all open jobs on GitHub
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @sakluger / @trjExpensifyThe text was updated successfully, but these errors were encountered: