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-04-17] IOU - After moving IOU the status in expense details is inconsistent on the Admin side #59210
Version Number: v9.1.19-5 Reproducible in staging?: Yes Reproducible in production?: No If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: Yes, reproducible on both If this was caught during regression testing, add the test name, ID and link from TestRail:#58078 Email or phone of affected tester (no customers): N/A Issue reported by: Applause Internal Team Device used: Pixel 7 Pro /Android 15 App Component: Money Requests
Action Performed:
Pre-requisite: A workspace with an admin and an employee
The workflow setting: enables Approvals, Delay Submissions is set to Manual, and enables Payment.
[Employee] Request money (IOU) from admin - DM
[Employee] Open the IOU report, copy the URL, add /change-workspace to the end of it, and send it as a message to the report
[Employee] Click the URL to open the Change Workspace RHP
Move the IOU report to the workspace the employee is a member of
Expected Result:
Verify that the IOU report was converted to an Expense report
Verify that the report preview was removed from the DM and added to the user's workspace chat
Actual Result:
The expense detail on the employee status: "waiting for Admin approve expense", but in the Admin shows the "Pay with expensify" button, and below still has "waiting for You approve 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 [-]IOU - After moving IOU the status in expense details is inconsistent on the Admin side[/-][+][Due for payment 2025-04-17] IOU - After moving IOU the status in expense details is inconsistent on the Admin side[/+]on Apr 10, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.25-4 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
@luacmartins@adelekennedy@luacmartins 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]
Skipping the payment summary for this issue since all the assignees are employees or vendors. If this is incorrect, please manually add the payment summary SO.
Activity
melvin-bot commentedon Mar 27, 2025
Triggered auto assignment to @adelekennedy (
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 Mar 27, 2025
Triggered auto assignment to @Gonals (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Mar 27, 2025
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon Mar 27, 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:
izarutskaya commentedon Mar 27, 2025
Production
bandicam.2025-03-27.12-47-42-012.mp4
39 remaining items
[-]IOU - After moving IOU the status in expense details is inconsistent on the Admin side[/-][+][Due for payment 2025-04-17] IOU - After moving IOU the status in expense details is inconsistent on the Admin side[/+]melvin-bot commentedon Apr 10, 2025
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Apr 10, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.25-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-04-17. 🎊
melvin-bot commentedon Apr 10, 2025
@luacmartins @adelekennedy @luacmartins 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]
melvin-bot commentedon Apr 17, 2025
Skipping the payment summary for this issue since all the assignees are employees or vendors. If this is incorrect, please manually add the payment summary SO.
luacmartins commentedon Apr 18, 2025
no payments needed for this one. closing.