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-07] [Due for payment 2025-04-03] [$250] Expense - Amount is cleared when sending to a conversation after creating expense in FAB #59130
Version Number: v9.1.19-0 Reproducible in staging?: Yes Reproducible in production?: No If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: N/A If this was caught during regression testing, add the test name, ID and link from TestRail: N/A Email or phone of affected tester (no customers): N/A Issue reported by: Applause Internal Team Device used: Windows 11/ Chrome, Android 13/ Chrome App Component: Money Requests
Action Performed:
Sign in to staging.new.expensify.com
Click on FAB > Create expense
Enter amount and Click next
Edit the "To" section to send expense to a non workspace conversation/ oneself
Expected Result:
Prompt to enter merchant is removed and expense confirmation page is displayed.
Actual Result:
Expense creation flow returns to entering amount and previously entered amount is cleared.
👋 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 [-]Expense - Amount is cleared when sending to a conversation after creating expense in FAB[/-][+][$250] Expense - Amount is cleared when sending to a conversation after creating expense in FAB[/+]on Mar 26, 2025
changed the title [-][$250] Expense - Amount is cleared when sending to a conversation after creating expense in FAB[/-][+][Due for payment 2025-04-03] [$250] Expense - Amount is cleared when sending to a conversation after creating expense in FAB[/+]on Mar 27, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.19-5 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
@nkuoch@NicMendonca@nkuoch 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]
changed the title [-][Due for payment 2025-04-03] [$250] Expense - Amount is cleared when sending to a conversation after creating expense in FAB[/-][+][Due for payment 2025-04-07] [Due for payment 2025-04-03] [$250] Expense - Amount is cleared when sending to a conversation after creating expense in FAB[/+]on Mar 31, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.20-2 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
@nkuoch@NicMendonca@nkuoch 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 Mar 26, 2025
Triggered auto assignment to @nkuoch (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Mar 26, 2025
Triggered auto assignment to @NicMendonca (
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 26, 2025
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon Mar 26, 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:
[-]Expense - Amount is cleared when sending to a conversation after creating expense in FAB[/-][+][$250] Expense - Amount is cleared when sending to a conversation after creating expense in FAB[/+]melvin-bot commentedon Mar 26, 2025
Job added to Upwork: https://www.upwork.com/jobs/~021904810130739309423
15 remaining items
[-][$250] Expense - Amount is cleared when sending to a conversation after creating expense in FAB[/-][+][Due for payment 2025-04-03] [$250] Expense - Amount is cleared when sending to a conversation after creating expense in FAB[/+]melvin-bot commentedon Mar 27, 2025
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Mar 27, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.19-5 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-03. 🎊
melvin-bot commentedon Mar 27, 2025
@nkuoch @NicMendonca @nkuoch 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]
[-][Due for payment 2025-04-03] [$250] Expense - Amount is cleared when sending to a conversation after creating expense in FAB[/-][+][Due for payment 2025-04-07] [Due for payment 2025-04-03] [$250] Expense - Amount is cleared when sending to a conversation after creating expense in FAB[/+]melvin-bot commentedon Mar 31, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.20-2 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-07. 🎊
melvin-bot commentedon Mar 31, 2025
@nkuoch @NicMendonca @nkuoch 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]