Submit expenses to updated approver when Processing for original approver already exists

[garrettmknight]

If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!

---

Version Number: All
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL: N/A
Issue reported by: @garrettmknight
Slack conversation: https://expensify.slack.com/archives/C036QM0SLJK/p1716909164800879

Action Performed:

Pre-reqs:

• Workspace on Instant Submit
• Approver set to Approver A

1. As submitter, create an expense in your workspace chat.
2. The expense is assigned to Approver A.
3. As an admin, change the approver for the workspace to Approver B.
4. As a submitter, create another expense in the workspace chat

Expected Result:

Expense #2 should be assigned to Approver B.

Actual Result:

Expense #2 is added to the existing report assigned to Approver A.

Workaround:

Approver A needs to approve the report in order for a new report assigned to Approver B to be created.

Platforms:

All

View all open jobs on GitHub

[melvin-bot]

Current assignee @garrettmknight is eligible for the Bug assigner, not assigning anyone new.

[garrettmknight]

Awaiting a volunteer - will probably clean this up as part of Instant Submit for Control.

[garrettmknight]

We decided not to change this behavior since it could be seen as expected. The core problem we'll need to solve is really moving reports from one approver to another in the case that the original approver is not longer able to approve. I think that will fit under a different project.