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-06-05] [Due for payment 2025-06-04] [$250] Unreported per diem expense can be submitted to user, incorrect redirection with RHP back button on the confirmation page #62727
Version Number: 9.1.51-0 Reproducible in staging?: Yes Reproducible in production?: Unable to check, new feature If this was caught during regression testing, add the test name, ID and link from TestRail:#58020 Email or phone of affected tester (no customers):applausetester+sjdoidwsn11j12@applause.expensifail.com Issue reported by: Applause Internal Team Device used: Mac 15.4 / Chrome App Component: Money Requests
Action Performed:
Precondition:
Log in with Expensifail account.
Workspace has per diem rates.
Go to staging.new.expensify.com
Go to workspace chat.
Create two per diem expenses in the workspace chat.
Click on the expense preview to go to expense report.
Click More > Delete.
Delete the report.
Go to self DM.
Click on the per diem expense.
Click on the report header.
Click Submit it to someone.
Select a user (not workspace).
Note that selecting a user is possible when submitting unreported per diem expense.
Click app back button.
Not here page opens.
Click app back button again.
Click Submit it to someone.
Select a workspace.
Click RHP back button on the confirmation page.
Note that RHP back button returns to per diem expense creation flow.
Expected Result:
In Step 12, user should not be able to select another user to submit unreported per diem expense.
In Step 14, RHP back button on confirmation page should return to report details page.
In Step 18, per diem expense receipt should not appear on the confirmation page.
In Step 19, RHP back button on confirmation page should return to report details page.
Actual Result:
In Step 12, user is able to select another user to submit unreported per diem expense.
In Step 14, RHP back button on confirmation page opens not here page when a user is selected.
In Step 18, per diem expense receipt appears on the confirmation page.
In Step 19, RHP back button on confirmation page returns to per diem expense creation flow.
👋 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.
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.52-0 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
@jayeshmangwani@sonialiap@jayeshmangwani 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-06-04] [$250] Unreported per diem expense can be submitted to user, incorrect redirection with RHP back button on the confirmation page[/-][+][Due for payment 2025-06-05] [Due for payment 2025-06-04] [$250] Unreported per diem expense can be submitted to user, incorrect redirection with RHP back button on the confirmation page[/+]on May 29, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.53-7 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
@jayeshmangwani@sonialiap@jayeshmangwani 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]
PR was CP'd to staging, but there's still the back button functionality to fix - I'm opening the issue up for external contributors so they can help with that!
The issue was external, and I posted the proposal at this time (10:17 PM)
Here is the time the PR was created (11:53 PM),
and the solution that is used to fix this issue is the same as my main solution
@mkzie2 , for future timelines, please link to the time stamped comment to make it a lil easier to find.
Rephrasing your summary as to provide reasoning of payment
Issue made External
You submitted proposal
Another PR fixed the issue
Other PR used your solution
You are due 50%, $125, because "You did the job of proposing a solution that was viable. We added External without knowing there was another issue or PR that was being worked on".
Activity
melvin-bot commentedon May 24, 2025
Triggered auto assignment to @sonialiap (
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 May 24, 2025
Triggered auto assignment to @mjasikowski (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon May 24, 2025
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon May 24, 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:
mjasikowski commentedon May 26, 2025
Working on a fix
24 remaining items
melvin-bot commentedon May 28, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.52-0 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-06-04. 🎊
For reference, here are some details about the assignees on this issue:
melvin-bot commentedon May 28, 2025
@jayeshmangwani @sonialiap @jayeshmangwani 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-06-04] [$250] Unreported per diem expense can be submitted to user, incorrect redirection with RHP back button on the confirmation page[/-][+][Due for payment 2025-06-05] [Due for payment 2025-06-04] [$250] Unreported per diem expense can be submitted to user, incorrect redirection with RHP back button on the confirmation page[/+]melvin-bot commentedon May 29, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.53-7 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-06-05. 🎊
For reference, here are some details about the assignees on this issue:
melvin-bot commentedon May 29, 2025
@jayeshmangwani @sonialiap @jayeshmangwani 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]
mallenexpensify commentedon Jun 6, 2025
@mkzie2 can you provide more details and a timeline, with links? We also have this issue which was fixed by the same PR
melvin-bot commentedon Jun 7, 2025
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸
mkzie2 commentedon Jun 7, 2025
@mallenexpensify Here is the timeline
and the solution that is used to fix this issue is the same as my main solution
mallenexpensify commentedon Jun 9, 2025
@mkzie2 , for future timelines, please link to the time stamped comment to make it a lil easier to find.
Rephrasing your summary as to provide reasoning of payment
You are due 50%, $125, because "You did the job of proposing a solution that was viable. We added
Externalwithout knowing there was another issue or PR that was being worked on".@mkzie2 can you please accept the job and reply here once you have?
https://www.upwork.com/jobs/~021927016765901331120
mkzie2 commentedon Jun 10, 2025
@mallenexpensify Thanks for helping! I accepted the job.
mallenexpensify commentedon Jun 11, 2025
Contributor: @mkzie2 paid $125 via Upwork