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
[Due for payment 2025-08-15] [RCA #65740] Invoice - Message sent by sender & receiver show the same invoice room avatar #67879
Version Number: 9.1.89-1 Reproducible in staging?: Yes Reproducible in production?: No If this was caught during regression testing, add the test name, ID and link from TestRail: Exp #65740 Email or phone of affected tester (no customers):sdjnsoidoijs1@gmail.com Issue reported by: Applause Internal Team Device used: Mac 15.5 / Chrome App Component: Money Requests
Action Performed:
Precondition:
Invoice feature is enabled.
Go to staging.new.expensify.com
[User A] Open FAB > Send invoice.
[User A] Send an invoice to User B.
[User A & User B] Open the invoice report and send a message.
Expected Result:
Message sent by User A & User B will show their respective avatar.
Actual Result:
Message sent by User A & User B show the same invoice room avatar.
👋 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.
changed the title [-] [RCA #65740] Invoice - Message sent by sender & receiver show the same invoice room avatar[/-][+][Due for payment 2025-08-15] [RCA #65740] Invoice - Message sent by sender & receiver show the same invoice room avatar[/+]on Aug 8, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.90-11 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
@grgia@lydiabarclay@JakubKorytko The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]
Activity
melvin-bot commentedon Aug 5, 2025
Triggered auto assignment to @lydiabarclay (
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 Aug 5, 2025
Triggered auto assignment to @marcaaron (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Aug 5, 2025
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon Aug 5, 2025
👋 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:
5 remaining items
grgia commentedon Aug 5, 2025
Fixed on staging, closing!
[-] [RCA #65740] Invoice - Message sent by sender & receiver show the same invoice room avatar[/-][+][Due for payment 2025-08-15] [RCA #65740] Invoice - Message sent by sender & receiver show the same invoice room avatar[/+]melvin-bot commentedon Aug 8, 2025
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Aug 8, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.90-11 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 2025-08-15. 🎊
For reference, here are some details about the assignees on this issue:
melvin-bot commentedon Aug 8, 2025
@grgia @lydiabarclay @JakubKorytko The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]