Skip to content

Expense - Next step message is not updated after moving the submitted expense #71732

Closed

Description

@jponikarchuk

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: V9.2.22-1
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from TestRail: https://test-management.browserstack.com/projects/2219752/test-runs/TR-1122/folder/13176730/41237112/929688261
Email or phone of affected tester (no customers): Slottwo1 hf-%rffffvrvvtfvd@gmail.comhttps://test-management.browserstack.com/projects/2219752/test-runs/TR-1122/folder/13176730/41237112/929688261
Issue reported by: Applause Internal Team
Device used: Redminote 10s android 13 phone
App Component: Money Requests

Action Performed:

  1. Go to https://staging.new.expensify.com/home
  2. Open Workspace chat
  3. Create 2 reports
  4. Create an expense in the first report
  5. Submit the expense
  6. Open the expense and tap reports field
  7. Move the expense to second report
  8. Note the header message
  9. Tap more

Expected Result:

Hourglass message must be updated after moving the submitted expense.
Retract option must not be available in more section.

Actual Result:

Hourglass message is not updated after moving the submitted expense.

Retract option is available in more section.

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

11.mp4
2.mp4

View all open jobs on GitHub

Activity

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

    @melvin-bot

    Triggered auto assignment to @clarajones-expensify (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. ShridharGoel commented on Oct 2, 2025

    @ShridharGoel
    Contributor

    Duplicate of #70926

  4. daledah commented on Oct 2, 2025

    @daledah
    Contributor

    this PR should also fix this issue

  5. clarajones-expensify commented on Oct 2, 2025

    @clarajones-expensify
    Contributor

    Closing this out then!

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

Metadata

Metadata

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