You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Send invoice - Workspace avatar and name are incorrect after paying invoice as a business #44806
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.
Go to staging.new.expensify.com
[User A] Send invoice to User B.
[User B] Go to invoice chat.
[User B] Click on the pay button > Pay as a business > Pay elsewhere.
[User B] After invoice chat avatar is changed, click on the chat header.
[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?
👋 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:
Identify the pull request that introduced this issue and revert it.
@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
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
Activity
melvin-bot commentedon Jul 4, 2024
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.melvin-bot commentedon Jul 4, 2024
Triggered auto assignment to @Beamanator (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.github-actions commentedon Jul 4, 2024
👋 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:
m-natarajan commentedon Jul 4, 2024
@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
m-natarajan commentedon Jul 4, 2024
We think that this bug might be related to #vip-vsb
Beamanator commentedon Jul 4, 2024
cc @cristipaval since you're the "Invoices in NewDot" guy!
3 remaining items
Beamanator commentedon Jul 4, 2024
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
Beamanator commentedon Jul 4, 2024
Also commented in #vip-billpay here
VickyStash commentedon Jul 8, 2024
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
JmillsExpensify commentedon Jul 10, 2024
Ah perfect, we'll keep an eye on that one.
cristipaval commentedon Jul 12, 2024
This is held.
cristipaval commentedon Jul 12, 2024
Actually, I think we can close this one, given that it was reproducible due to a PR that was reverted.