Skip to content

[$250] Approver - Sub-header link appears to Approver D after change approver #73181

@jponikarchuk

Description

@jponikarchuk

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: v9.2.36-0
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #72283
Email or phone of affected tester (no customers): [email protected]
Issue reported by: Applause Internal Team
Device used: Windows 11 Home/Chrome
App Component: Workspace Settings

Action Performed:

Prerequisites

  • Create a Collect plan workspace.
  • Invite 4 non-admin members. A, B, C and D.
  • Enable workflows.
  • Assign User C member as approver for workspace.
  • Member A create an expense to Workspace
  1. Open https://staging.new.expensify.com/
  2. As admin, go to expense report from Member A
  3. Click on 'More'
  4. Select 'Change Approver'
  5. Upgrade the Workspace and complete the flow
  6. Select Member D as new approver
  7. As Member D, open the expense report from Member A
  8. Click sub-header 'from...' link
  9. Navigate back to report expense

Expected Result:

At step 7, Member D should see the expense report without sub-header 'from...' link

Actual Result:

At step 7, the sub-header 'from...' link appears
At Step 8, it directs to 'Hmm. it's not here' page
At step 9, sub-header 'from...' link disappears

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

1.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~021984000454300180120
  • Upwork Job ID: 1984000454300180120
  • Last Price Increase: 2025-11-06
Issue OwnerCurrent Issue Owner: @roryabraham

Metadata

Metadata

Labels

BugSomething is broken. Auto assigns a BugZero manager.ExternalAdded to denote the issue can be worked on by a contributorWeeklyKSv2

Type

No type

Projects

Status

No status

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions