[Reject] Expense - Wrong next action message after resolving rejection

[vincdargento]

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): jsdoinjdsoisjdoi3@gmail.com
Issue reported by: Applause Internal Team
Device used: Mac 15.5 / Chrome
App Component: Money Requests

Action Performed:

1. Go to staging.new.expensify.com

2. Go to workspace chat.

3. Create an expense in workspace chat.

4. Open the expense report.

5. Click Submit.

6. Click More > Reject.

7. Enter reason and click Reject expense.

8. Click Mark as resolved.
   → BUG 1: The next action message is "Waiting for you to approve expense(s)." instead of "Waiting for you to submit expense(s)."

9. Go back to workspace chat and reopen the expense report.
   → BUG 2: The next action message changes to "Waiting for you to fix issue(s)." instead of "Waiting for you to submit expense(s)."

Expected Result:

BUG 1: After resolving the rejection, the next action message is "Waiting for you to submit expense(s)."
BUG 2: After reopening the expense report, the next action message is "Waiting for you to submit expense(s)."

Actual Result:

BUG 1: After resolving the rejection, the next action message is "Waiting for you to approve expense(s)." instead of "Waiting for you to submit expense(s)."
BUG 2: After reopening the expense report, the next action message is "Waiting for you to fix issue(s)." instead of "Waiting for you to submit expense(s)."

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

bug.mp4

View all open jobs on GitHub

[melvin-bot]

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

[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]

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

[melvin-bot]

Triggered auto assignment to @lschurr (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.

[vincdargento]

@lschurr FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors.