Skip to content

Expense - "marked as paid" message thread opens incorrectly on top, replies are not seen #71416

Closed

Description

@mitarachim

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.19-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from TestRail: #71084
Email or phone of affected tester (no customers): sjdniodsjonisjodjs1@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. Open 1:1 DM.
  3. Click + > Pay.
  4. Enter amount > Next.
  5. Click Mark as paid.
  6. Open the expense report.
  7. Right click on "marked as paid" message > Reply in thread.
  8. Send a reply in thread.

Expected Result:

In Step 7, "marked as paid" message thread will open at the bottom.
In Step 8, reply will be visible.

Actual Result:

In Step 7, "marked as paid" message thread opens incorrectly on top.
In Step 8, reply is not visible.

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

Bug6957186_1758934703983.Screen_Recording_2025-09-27_at_08.57.48.mp4

View all open jobs on GitHub

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    DeployBlockerIndicates it should block deploying the API
    on Sep 27, 2025
  2. melvin-bot commented on Sep 27, 2025

    @melvin-bot

    Triggered auto assignment to @mallenexpensify (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. melvin-bot commented on Sep 27, 2025

    @melvin-bot

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

  4. melvin-bot commented on Sep 27, 2025

    @melvin-bot

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

  5. github-actions commented on Sep 27, 2025

    @github-actions
    Contributor

    👋 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.
  6. added and removed
    DeployBlockerCashThis issue or pull request should block deployment
    DeployBlockerIndicates it should block deploying the API
    on Sep 28, 2025
  7. Gonals commented on Sep 28, 2025

    @Gonals
    Contributor

    I don't think we need to block on this

  8. izarutskaya commented on Sep 29, 2025

    @izarutskaya

    Issue is not reproducible
    Mac os 10.15.7 chrome
    Build 9.2.19-2

    Screen.Recording.2025-09-29.At.17.28.43.mp4

    Issue is not reproducible on Samsung S23FE/ Chrome
    Build 9.2.19-2

    71416.mp4
  9. mountiny commented on Sep 29, 2025

    @mountiny
    Contributor

    Going to close this one as we are going to handle the fix in a new PR #63253 (comment)

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.EngineeringReviewingHas a PR in reviewWeeklyKSv2

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions