Skip to content

Send invoice - Workspace avatar and name are incorrect after paying invoice as a business #44806

Closed

Description

@m-natarajan

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


issue found when validating #43036
Version Number: 9.0.4-0
Reproducible in staging?: y
Reproducible in production?: n
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause internal team
Slack conversation:

Action Performed:

Precondition:

  • User A and User B have their own workspaces.
  1. Go to staging.new.expensify.com
  2. [User A] Send invoice to User B.
  3. [User B] Go to invoice chat.
  4. [User B] Click on the pay button > Pay as a business > Pay elsewhere.
  5. [User B] After invoice chat avatar is changed, click on the chat header.
  6. [User B] Click on User B's workspace avatar.

Expected Result:

User B's workspace avatar will be displayed with the correct workspace name.

Actual Result:

User B's workspace avatar is displayed as User A's workspace avatar together with User A's workspace name

Workaround:

unknown

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

Bug6532627_1720057227037.20240704_093524.mp4

View all open jobs on GitHub

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    DeployBlockerIndicates it should block deploying the API
    on Jul 4, 2024
  2. melvin-bot commented on Jul 4, 2024

    @melvin-bot

    Triggered auto assignment to @JmillsExpensify (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. melvin-bot commented on Jul 4, 2024

    @melvin-bot

    Triggered auto assignment to @Beamanator (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

  4. github-actions commented on Jul 4, 2024

    @github-actions
    Contributor

    👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

    1. Identify the pull request that introduced this issue and revert it.
    2. Find someone who can quickly fix the issue.
    3. Fix the issue yourself.
  5. m-natarajan commented on Jul 4, 2024

    @m-natarajan
    Author

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

  6. m-natarajan commented on Jul 4, 2024

    @m-natarajan
    Author

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

  7. Beamanator commented on Jul 4, 2024

    @Beamanator
    Contributor

    cc @cristipaval since you're the "Invoices in NewDot" guy!

  8. 3 remaining items

  9. Beamanator commented on Jul 4, 2024

    @Beamanator
    Contributor

    Marking NAB b/c of @cristipaval 's comment in the PR here. Keeping this open till we determine if it's needed or if we're going to handle this case in the issue linked to that PR

  10. Beamanator commented on Jul 4, 2024

    @Beamanator
    Contributor

    Also commented in #vip-billpay here

  11. VickyStash commented on Jul 8, 2024

    @VickyStash
    Contributor

    I was able to reproduce this issue, and I'm going to fix it in the upcoming PR related to Pay as business functionality.
    cc @cristipaval

  12. JmillsExpensify commented on Jul 10, 2024

    @JmillsExpensify
    Contributor

    Ah perfect, we'll keep an eye on that one.

  13. cristipaval commented on Jul 12, 2024

    @cristipaval
    Contributor

    This is held.

  14. cristipaval commented on Jul 12, 2024

    @cristipaval
    Contributor

    Actually, I think we can close this one, given that it was reproducible due to a PR that was reverted.

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

Metadata

Metadata

Labels

BugSomething is broken. Auto assigns a BugZero manager.DailyKSv2Engineering

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions