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
[$250] Split expense - Reimbursable is enabled in split preview when it is disabled during creation #68837
Version Number: 9.1.97-1 Reproducible in staging?: Yes Reproducible in production?: N/A - new feature, doesn't exist in prod If this was caught during regression testing, add the test name, ID and link from TestRail:#68581 Email or phone of affected tester (no customers):applausetester+140823khh@applause.expensifail.com Issue reported by: Applause Internal Team Device used: Mac 15.5 / Chrome App Component: Money Requests
Action Performed:
Precondition:
Log in with Expensifail account.
Go to staging.new.expensify.com
Go to Account > Save the world.
Click I am a teacher.
Enter name and work email (any expensifail account).
Once landed in Teachers Unite workspace chat, click +.
If Split expense option disappears, refresh the page.
Click + > Split expense.
Enter amount > Next.
On confirm page, enter merchant and disable Reimbursable toggle.
Click Split button.
Open split preview and transaction thread.
Expected Result:
Reimbursable toggle will be disabled in split preview and transaction thread because it is created with reimbursable disabled on confirm page (Step 9).
Actual Result:
Reimbursable toggle is enabled in split preview and transaction thread when it is created with reimbursable disabled on confirm page (Step 9).
👋 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.
Yeah, TU workspace is the only place you can do a P2P style "split expense" on a workspace right now. Totally agree this is an edge case and can be demoted.
Activity
melvin-bot commentedon Aug 20, 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.github-actions commentedon Aug 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 Aug 20, 2025
Triggered auto assignment to @neil-marcellini (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Aug 20, 2025
💬 A slack conversation has been started in #expensify-open-source
daledah commentedon Aug 20, 2025
We need expected behaviour in this case 👀
flaviadefaria commentedon Aug 20, 2025
This is definitely not a deploy blocker.
Also @jponikarchuk is this only reproducible when going to
Account > Save the worldor also from any other workspace (Collect/Control)?trjExpensify commentedon Aug 20, 2025
Yeah, TU workspace is the only place you can do a P2P style "split expense" on a workspace right now. Totally agree this is an edge case and can be demoted.
94 remaining items
neil-marcellini commentedon Dec 9, 2025
Yeah that does sound like the problem. I will investigate.
neil-marcellini commentedon Dec 9, 2025
Ah wow this is a funny one!
I supportaled in and found the data from the teacher's unit test policyID
ABD1345ED7293535. When on staging we use the test policyThat's why we see
disabledFields.reimbursable == falseThe data is properly set for the prod policyID
B795B6319125BDF2I think we'll need @sonialiap to fix the setting on the test policy (
ABD1345ED7293535) and then we should be all good.sonialiap commentedon Dec 16, 2025
Noting for myself:
ABD1345ED7293535is owned byvolunteer@expensify.orgI changed from
reimbursable by defaulttoalways reimbursablesonialiap commentedon Dec 16, 2025
Retest requested
m-natarajan commentedon Dec 16, 2025
No Reimbursement toggle, MacOS Monterey / Chrome, Xiaomi Redmi Note 10 / Android 12, iPhone 13 / iOS 18.7.1, v9.2.78-6
IMG_0441.MP4
Screenrecorder-2025-12-16-16-01-42-257.mp4
Screen.Recording.2025-12-16.at.15.49.53.mp4
melvin-bot commentedon Dec 19, 2025
@sonialiap Whoops! This issue is 2 days overdue. Let's get this updated quick!
neil-marcellini commentedon Dec 22, 2025
Ok, I think this is fixed. Closing it. We can re-open if needed for some reason.