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
Split - Split from the deleted workspace opens not here page when opened from Edit splits page #72066
Version Number: 9.2.27-0 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:#63738 Email or phone of affected tester (no customers):applausetester+jdoisjs1@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.
Create two workspaces.
Go to staging.new.expensify.com
Go to the second workspace chat.
Create an empty report via + > Create report.
Go to the first workspace chat.
Create an expense.
Open the expense report.
Click More > Split.
Click Save.
Open any split.
Click Report and select the empty report from the second workspace.
Delete the second workspace.
Go back to the remaining split in the first workspace chat.
Click More > Edit splits.
Click on the other split (not highlighted).
Expected Result:
The split from the deleted workspace should be removed from Edit splits page if it cannot be edited.
Actual Result:
The split from the deleted workspace opens not here page when opened from Edit splits page.
👋 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.
@ZhenjaHorbach is this the same limit we're facing in the other one where it's technically off workspace so our check isn't allowing access to the split table?
@ZhenjaHorbach is this the same limit we're facing in the other one where it's technically off workspace so our check isn't allowing access to the split table?
Activity
melvin-bot commentedon Oct 8, 2025
Triggered auto assignment to @trjExpensify (
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 Oct 8, 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 Oct 8, 2025
Triggered auto assignment to @puneetlath (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Oct 8, 2025
💬 A slack conversation has been started in #expensify-open-source
ZhenjaHorbach commentedon Oct 8, 2025
This feature is in beta
So I suppose we can remove the deploy blocker label here
ZhenjaHorbach commentedon Oct 8, 2025
@garrettmknight
Could you help with the expected behaviour here?
garrettmknight commentedon Oct 8, 2025
The expected behavior is that the user should still be able to edit the expense. This is what it looks like for a non-split expense:
https://github.com/user-attachments/assets/eee17deb-2fae-4ac3-905c-2a48a8383394
Can you investigate and see why we're hitting a
Not hereinstead of being able to edit the expense?garrettmknight commentedon Oct 8, 2025
@ZhenjaHorbach is this the same limit we're facing in the other one where it's technically off workspace so our check isn't allowing access to the split table?
ZhenjaHorbach commentedon Oct 8, 2025
Yeah
This issue is similar to this one
garrettmknight commentedon Oct 8, 2025
Cool, I've created a separate follow-up issue for us to enable Split on unreported expenses. #72125