Rejected expense moved to submitter's self DM with instant submissions in WS

[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.14-2
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: #62787
Email or phone of affected tester (no customers): N/A
Issue reported by: Applause Internal Team
Device used: Web Chrome, Desktop, mWeb Safari, iOS
App Component: Other

Action Performed:

Preconditions: Admin and Employee are both expensifail accounts
Admin:

• created a collect WS in OD.
• Workspace Scheduled Submit enabled, frequency is set to Instant
• added a member
  Member:
• created a report in the WS chat,
• added three expenses.
• No draft report exists in the workspace.

1. Sign in to ND as an Admin
2. Open the expense report with multiple expenses, open any expense
3. Reject the expense
4. Verify a new draft report is created and the expense is moved there.

Expected Result:

A new draft report is created and the expense is moved there (PR section C, step 5)

Actual Result:

Rejected expense was moved to the member's self DM, new report was not created

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

Bug6945481_1757975871810.PR_instant_submit.mp4

View all open jobs on GitHub

[melvin-bot]

Triggered auto assignment to @stephanieelliott (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]

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

[melvin-bot]

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

[melvin-bot]

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