Skip to content

Expense - Wrong approver in the next step message when report is opened as second approver #72801

Closed

Description

@lanitochka17

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.32-1
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail: #70283
Email or phone of affected tester (no customers): jdsoijsdoijsojsdoijs2@gmail.com
Issue reported by: Applause - Internal Team

Action Performed:

Precondition:

  • User A invites User B to the workspace
  • Edit the existing approval workflow so that User A is the first approver and User B is the second approver
  1. Go to staging.new.expensify.com
  2. [User B] Create an expense in the workspace chat
  3. [User B] Open the expense report and click Submit
  4. [User A] Open the expense report
  5. [User A] Click Approve
    → Next step message shows "Waiting for User B to approve expenses" - Expected behavior
  6. [User B] Open the expense report

Expected Result:

User B will see the same approver in the next step message "Waiting for User B to approve expenses" because User B is the second approver

Actual Result:

User B sees User A as the next approver in the next step message "Waiting for User A to approve expenses" when User B is the second approver

Workaround:

Unknown

Platforms:

Select the officially supported platforms where the issue was reproduced:

  • Android: App
  • Android: mWeb Chrome
  • iOS: App
  • iOS: mWeb Safari
  • iOS: mWeb Chrome
  • Windows: Chrome
  • MacOS: Chrome / Safari
  • MacOS: Desktop
Platforms Tested: On which of our officially supported platforms was this issue tested:
  • Android: App
  • Android: mWeb Chrome
  • iOS: App
  • iOS: mWeb Safari
  • iOS: mWeb Chrome
  • Windows: Chrome
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence
Bug6976599_1760620382258.Screen_Recording_2025-10-16_at_21.03.18.mp4

View all open jobs on GitHub

Activity

  1. added
    BugSomething is broken. Auto assigns a BugZero manager.
    on Oct 16, 2025
  2. melvin-bot commented on Oct 16, 2025

    @melvin-bot

    Triggered auto assignment to @twisterdotcom (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. twisterdotcom commented on Oct 17, 2025

    @twisterdotcom
    Contributor

    I need to test this.

  4. twisterdotcom commented on Oct 20, 2025

    @twisterdotcom
    Contributor

    Okay, looks like this was reverted.

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

Metadata

Metadata

Assignees

Labels

BugSomething is broken. Auto assigns a BugZero manager.DailyKSv2

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions