Skip to content

[HOLD for payment 2024-06-05] [$250] Merge account - Email for merged account is prefixed with 0@ in archived workspace chat #40977

Closed

Description

@kbecciv

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:

  1. Go to staging.new.expensify.com
  2. [Admin] Invite User A and B to the workspace.
  3. [Admin] Remove User A from the workspace.
  4. [User B] Go to Old Dot.
  5. [User B] Merge account with User A.
  6. [User B] Return to New Dot.
  7. [User B] Open workspace chat with User A (after merging).

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?

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

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
  • Upwork Job URL: https://www.upwork.com/jobs/~01e83a7aa224f88987
  • Upwork Job ID: 1785403324396785664
  • Last Price Increase: 2024-05-14
  • Automatic offers:
    • getusha | Reviewer | 0
Issue OwnerCurrent Issue Owner: @sakluger / @trjExpensify

Activity

  1. added
    BugSomething is broken. Auto assigns a BugZero manager.
    on Apr 25, 2024
  2. melvin-bot commented on Apr 25, 2024

    @melvin-bot

    Triggered auto assignment to @sakluger (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

  3. kbecciv commented on Apr 25, 2024

    @kbecciv
    Author

    We think that this bug might be related to #vip-vsb

  4. kbecciv commented on Apr 25, 2024

    @kbecciv
    Author

    @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.

  5. melvin-bot commented on Apr 30, 2024

    @melvin-bot

    @sakluger Huh... This is 4 days overdue. Who can take care of this?

  6. sakluger commented on Apr 30, 2024

    @sakluger
    Contributor

    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.

  7. added
    ExternalAdded to denote the issue can be worked on by a contributor
    on Apr 30, 2024
  8. changed the title [-]Merge account - Email for merged account is prefixed with 0@ in archived workspace chat[/-] [+][$250] Merge account - Email for merged account is prefixed with 0@ in archived workspace chat[/+] on Apr 30, 2024
  9. melvin-bot commented on Apr 30, 2024

    @melvin-bot
  10. 65 remaining items

  11. sakluger commented on Jun 5, 2024

    @sakluger
    Contributor

    @getusha is that being tracked anywhere? Do you know how much longer until you are moved to NewDot payments?

  12. sakluger commented on Jun 5, 2024

    @sakluger
    Contributor

    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?

  13. added and removed on Jun 5, 2024
  14. sakluger commented on Jun 14, 2024

    @sakluger
    Contributor

    Still on hold.

  15. sakluger commented on Jun 24, 2024

    @sakluger
    Contributor

    Hey @getusha - any updates here, or are you still waiting to get set up on NewDot payments?

  16. JmillsExpensify commented on Jun 25, 2024

    @JmillsExpensify
    Contributor

    Can I get a payment summary so that I can approve for @getusha

  17. sakluger commented on Jun 25, 2024

    @sakluger
    Contributor

    Summarizing payment on this issue:

    Contributor: @rezkiy37 $250, no payment required (contractor)
    Contributor+: @getusha $250, please request on Newdot

  18. JmillsExpensify commented on Jun 26, 2024

    @JmillsExpensify
    Contributor

    $250 approved for @getusha

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionBugSomething is broken. Auto assigns a BugZero manager.ExternalAdded to denote the issue can be worked on by a contributorWeeklyKSv2

Type

No type

Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions