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-07-17] [$250] Expense - App opens expense report after submitting per diem expense from empty report preview #64671
Version Number: 9.1.70-0 Reproducible in staging?: Yes Reproducible in production?: Unable to validate in Prod If this was caught during regression testing, add the test name, ID and link from TestRail:#64212 Email or phone of affected tester (no customers):applausetester+200602kh@applause.expensifail.com Issue reported by: Applause Internal Team Device used: Mac 15.5 / Chrome App Component: Money Requests
Action Performed:
Precondition:
Workspace has per diem rates.
Go to staging.new.expensify.com
Go to workspace chat.
Click + > Create report.
Click Add expense button on the expense preview.
Click Create new expense.
Switch to Per diem.
Select a destination and complete the flow to reach the confirmation page.
Click Create expense.
Expected Result:
After submitting the per diem expense, app will stay in the main workspace chat because user submits the expense from the main workspace chat. (This is the behavior when manual expense is submitted from the empty report preview in the main workspace chat).
Actual Result:
After submitting per diem expense from the empty report preview in the main workspace chat, app opens the expense report instead of staying in main workspace chat.
👋 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.
@NicMendonca 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.
changed the title [-][$250] Expense - App opens expense report after submitting per diem expense from empty report preview[/-][+][Due for payment 2025-07-17] [$250] Expense - App opens expense report after submitting per diem expense from empty report preview[/+]on Jul 10, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.78-4 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
@allgandalf@NicMendonca 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]
1a. Result of the original design (eg. a case wasn't considered)
1b. Mistake during implementation
1c. Backend bug
1z. Other:
Where bug was reported:
2a. Reported on production (eg. bug slipped through the normal regression and PR testing process on staging)
2b. Reported on staging (eg. found during regression or PR testing)
2d. Reported on a PR
2z. Other:
Who reported the bug:
3a. Expensify user
3b. Expensify employee
3c. Contributor
3d. QA
3z. Other:
[Contributor] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.
Link to comment: NO offending PR , check this comment
[Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.
Link to discussion: N/A
[Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.
[BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.
Link to issue:
Regression Test Proposal
Precondition:
Workspace has per diem rates.
Test:
Go to workspace chat.
Click + > Create report.
Click Add expense button on the expense preview.
Click Create new expense.
Switch to Per diem.
Select a destination and complete the flow to reach the confirmation page.
Click Create expense.
Verify that After submitting the per diem expense, app will stay in the main workspace chat.
Activity
github-actions commentedon Jun 20, 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 Jun 20, 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 Jun 20, 2025
Triggered auto assignment to @JS00001 (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Jun 20, 2025
💬 A slack conversation has been started in #expensify-open-source
vincdargento commentedon Jun 20, 2025
@NicMendonca 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.
23 remaining items
allgandalf commentedon Jul 4, 2025
PR approved
[-][$250] Expense - App opens expense report after submitting per diem expense from empty report preview[/-][+][Due for payment 2025-07-17] [$250] Expense - App opens expense report after submitting per diem expense from empty report preview[/+]melvin-bot commentedon Jul 10, 2025
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Jul 10, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.78-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-07-17. 🎊
For reference, here are some details about the assignees on this issue:
melvin-bot commentedon Jul 10, 2025
@allgandalf @NicMendonca 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]
allgandalf commentedon Jul 13, 2025
BugZero Checklist:
Bug classification
Source of bug:
Where bug was reported:
Who reported the bug:
[Contributor] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.
Link to comment: NO offending PR , check this comment
[Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.
Link to discussion: N/A
[Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.
[BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.
Link to issue:
Regression Test Proposal
Precondition:
Test:
Verify that After submitting the per diem expense, app will stay in the main workspace chat.
Do we agree 👍 or 👎
allgandalf commentedon Jul 17, 2025
payment today!
NicMendonca commentedon Jul 17, 2025
Payment summary
Contributor: @FitseTLT - $250 via Upwork (done ✅ )
Contributor+: @allgandalf - $250 via Upwork (done ✅ )