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-09-19] Merge - Expense created on member´s side on different WS, shown on admin´s side when merging #68195
Version Number: 9.1.91-0 Reproducible in staging?: Yes Reproducible in production?: N/A - new feature, doesn't exist in prod If this was caught during regression testing, add the test name, ID and link from TestRail:#65596 Email or phone of affected tester (no customers):ibellicotest+1546@gmail.com Issue reported by: Applause Internal Team Device used: Motorola MotoG60 / Android 12 / Chrome ( mWeb / Hybrid app) - Windows 10 / Chrome App Component: Money Requests
Action Performed:
Prerequisite: User A, has at least one workspace created.
Prerequisite 2: User B, has at least one workspace created.
Open the Expensify app.
Log in as User A.
Navigate to "Workspaces" and open any workspace.
Tap on "Members" and invite User B as member.
As User B, open an owned workspace chat.
Submit a manual expense to it.
Also as User B, navigate to the workspace chat where User A is admin.
Submit a different manual expense to it.
As User A, open the expense created by User B.
Tap on "More" and select "Merge"
Note that the first expense created by User B, appears on the list, despite User A, not being part of the workspace where it was created.
Tap on the expense. and tap on "Continue"
Keep the amount from the selected expense.
Once redirected to report, note that the amount wasn´t changed.
Expected Result:
Admin of a workspace, shouldn´t be able to merge an expense created by a member, selecting an expense that belongs to a workspace from member´s account.
Actual Result:
When admin of a workspace, tries to merge an expense created by a member, an expense that belongs to a different workspace from member´s account, appears on the list, despite admin not being part of that workspace.
Also, amount is not changed after finishing the merging process selecting that expense.
👋 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 [-]Merge - Expense created on member´s side on different WS, shown on admin´s side when merging[/-][+][Due for payment 2025-09-19] Merge - Expense created on member´s side on different WS, shown on admin´s side when merging[/+]on Sep 12, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.12-4 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
@hoangzinh / @dominictb@muttmuure 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
github-actions commentedon Aug 8, 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:
melvin-bot commentedon Aug 8, 2025
Triggered auto assignment to @muttmuure (
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 8, 2025
Triggered auto assignment to @luacmartins (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Aug 8, 2025
💬 A slack conversation has been started in #expensify-open-source
22 remaining items
melvin-bot commentedon Aug 29, 2025
@hoangzinh, @youssef-lr, @muttmuure, @dominictb Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!
garrettmknight commentedon Sep 2, 2025
Fixed in this adhoc build: https://68204.pr-testing.expensify.com/
youssef-lr commentedon Sep 2, 2025
Not overdue.
melvin-bot commentedon Sep 11, 2025
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.
If a regression has occurred and you are the assigned CM follow the instructions here.
If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.
[-]Merge - Expense created on member´s side on different WS, shown on admin´s side when merging[/-][+][Due for payment 2025-09-19] Merge - Expense created on member´s side on different WS, shown on admin´s side when merging[/+]melvin-bot commentedon Sep 12, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.12-4 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-09-19. 🎊
For reference, here are some details about the assignees on this issue:
melvin-bot commentedon Sep 12, 2025
@hoangzinh / @dominictb @muttmuure 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]