Skip to content

Split - Split from the deleted workspace opens not here page when opened from Edit splits page #72066

Closed

Description

@mitarachim

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!


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.
  1. Go to staging.new.expensify.com
  2. Go to the second workspace chat.
  3. Create an empty report via + > Create report.
  4. Go to the first workspace chat.
  5. Create an expense.
  6. Open the expense report.
  7. Click More > Split.
  8. Click Save.
  9. Open any split.
  10. Click Report and select the empty report from the second workspace.
  11. Delete the second workspace.
  12. Go back to the remaining split in the first workspace chat.
  13. Click More > Edit splits.
  14. 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.

Workaround:

Unknown

Platforms:

  • Android: App
  • Android: mWeb Chrome
  • iOS: App
  • iOS: mWeb Safari
  • iOS: mWeb Chrome
  • Windows: Chrome
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Screenshots/Videos

Bug6968151_1759902955338.Screen_Recording_2025-10-08_at_13.52.30.mp4

View all open jobs on GitHub

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    DeployBlockerIndicates it should block deploying the API
    on Oct 8, 2025
  2. melvin-bot commented on Oct 8, 2025

    @melvin-bot

    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.

  3. github-actions commented on Oct 8, 2025

    @github-actions
    Contributor

    👋 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:

    1. Identify the pull request that introduced this issue and revert it.
    2. Find someone who can quickly fix the issue.
    3. Fix the issue yourself.
  4. melvin-bot commented on Oct 8, 2025

    @melvin-bot

    Triggered auto assignment to @puneetlath (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

  5. melvin-bot commented on Oct 8, 2025

    @melvin-bot

    💬 A slack conversation has been started in #expensify-open-source

  6. ZhenjaHorbach commented on Oct 8, 2025

    @ZhenjaHorbach
    Contributor

    This feature is in beta
    So I suppose we can remove the deploy blocker label here

  7. removed
    DeployBlockerCashThis issue or pull request should block deployment
    DeployBlockerIndicates it should block deploying the API
    on Oct 8, 2025
  8. ZhenjaHorbach commented on Oct 8, 2025

    @ZhenjaHorbach
    Contributor

    @garrettmknight
    Could you help with the expected behaviour here?

  9. garrettmknight commented on Oct 8, 2025

    @garrettmknight
    Contributor

    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 here instead of being able to edit the expense?

  10. garrettmknight commented on Oct 8, 2025

    @garrettmknight
    Contributor

    @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?

  11. ZhenjaHorbach commented on Oct 8, 2025

    @ZhenjaHorbach
    Contributor

    @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?

    Yeah
    This issue is similar to this one

  12. garrettmknight commented on Oct 8, 2025

    @garrettmknight
    Contributor

    Cool, I've created a separate follow-up issue for us to enable Split on unreported expenses. #72125

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

BugSomething is broken. Auto assigns a BugZero manager.DailyKSv2Engineering

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions