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-08-11] [$250] Expense - Report field on confirmation page shows submitted report, but the expense is created in a new report #62415
Version Number: 9.1.47-1 Reproducible in staging?: Yes Reproducible in production?: No 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):applausetester+200511kh@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.
Delayed submissions is set to Manually.
Add approvals is enabled.
Go to staging.new.expensify.com
Go to workspace chat.
Submit an expense.
Click Submit on the expense preview.
Click on the expense preview.
Click report header.
Click Title, rename and save it (to remember easily).
Go back to the main workspace chat.
Click + > Create expense > Manual.
Enter amount > Next.
On confirmation page, click Show more.
Note that Report field shows the expense report from Step 3.
Click Create expense.
Expected Result:
In Step 12, the Report field on the confirmation page should show a new report.
Actual Result:
In Step 12, the Report field on the confirmation page shows the submitted report from Step 3.
In Step 13, after submitting the expense, the expense is created in a new report, instead of the selected report as stated in Step 12.
👋 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.
@bfitzexpensify 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.
@cristipaval can you confirm what the behavior is here. It seems like we're making changes in this PR. But not clear whether it would be worse to revert that at this point or accept this minor inconsistency (feels like the latter).
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, this is a case wasn't considered before
[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:
[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:
Delayed submissions is set to Manually. Add approvals is enabled.
Test:
Go to workspace chat.
Submit an expense.
Click Submit on the expense preview.
Click + > Create expense > Manual.
Enter amount > Next.
On confirmation page, click Show more.
Verify that: In reports field, the Report field on the confirmation page should show a new report.
Activity
melvin-bot commentedon May 20, 2025
Triggered auto assignment to @bfitzexpensify (
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.github-actions commentedon May 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 May 20, 2025
Triggered auto assignment to @marcaaron (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon May 20, 2025
💬 A slack conversation has been started in #expensify-open-source
vincdargento commentedon May 20, 2025
@bfitzexpensify 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.
marcaaron commentedon May 20, 2025
This PR seems related...
#62003 – Fix "Pay" & "Approve" buttons inside the report & when expenses are held
Though, looking at the changes and I'm not too sure. This could be an API issue as well.
marcaaron commentedon May 20, 2025
@cristipaval can you confirm what the behavior is here. It seems like we're making changes in this PR. But not clear whether it would be worse to revert that at this point or accept this minor inconsistency (feels like the latter).
41 remaining items
bfitzexpensify commentedon Aug 12, 2025
@DylanDylann please complete the BZ checklist
Offer sent via Upwork @daledah
DylanDylann commentedon Aug 12, 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, this is a case wasn't considered before
[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:
[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:
Do we agree 👍 or 👎
bfitzexpensify commentedon Aug 13, 2025
Payment summary:
@DylanDylann due $250 via NewDot manual request
bfitzexpensify commentedon Aug 15, 2025
I am heading OOO until September 1st - adding a BZ buddy
Current status:
melvin-bot commentedon Aug 15, 2025
Triggered auto assignment to @CortneyOfstad (
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.CortneyOfstad commentedon Aug 19, 2025
Payment Summary
@daledah — paid $250 via Upwork
@DylanDylann – to be paid $250 via NewDot
Regression Test
https://github.com/Expensify/Expensify/issues/535788
quinthar commentedon Oct 17, 2025
Approved $250 to @DylanDylann