Skip to content

[HOLD https://github.com/Expensify/App/pull/60884] [Better Expense Report View] [$250] Expense - Paid system message thread opens when opening expense from "Pay someone" #60758

Closed

Description

@nlemma

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.1.32-0
Reproducible in staging?: Yes
Reproducible in production?: Unable to check - new feature testing
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: No, reproducible on hybrid only
If this was caught during regression testing, add the test name, ID and link from TestRail: #60119
Email or phone of affected tester (no customers): applausetester+cnmnmc2@applause.expensifail.com
Issue reported by: Applause Internal Team
Device used: Mac 15.3 / Chrome
App Component: Money Requests

Action Performed:

Precondition:

  • Log in with Expensifail account.
  1. Go to staging.new.expensify.com
  2. Go to 1:1 DM.
  3. Click + > Pay.
  4. Enter amount > Next.
  5. Click Pay elsewhere.
  6. Click on the expense preview.
  7. Click on the expense.

Expected Result:

Transaction thread will open.

Actual Result:

The thread of system message "paid elsewhere" opens instead.

Workaround:

Unknown

Platforms:

  • Android: Standalone
  • Android: HybridApp
  • Android: mWeb Chrome
  • iOS: Standalone
  • iOS: HybridApp
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Screenshots/Videos

Bug6811097_1745445947901.20250424_060219.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~021915478664281137065
  • Upwork Job ID: 1915478664281137065
  • Last Price Increase: 2025-04-24
Issue OwnerCurrent Issue Owner: @abdulrahuman5196

Activity

  1. added
    BugSomething is broken. Auto assigns a BugZero manager.
    DeployBlockerCashThis issue or pull request should block deployment
    on Apr 23, 2025
  2. melvin-bot commented on Apr 23, 2025

    @melvin-bot

    Triggered auto assignment to @VictoriaExpensify (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 Apr 23, 2025

    @melvin-bot

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

  4. melvin-bot commented on Apr 23, 2025

    @melvin-bot

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

  5. github-actions commented on Apr 23, 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. nlemma commented on Apr 23, 2025

    @nlemma
    Author

    @VictoriaExpensify 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.

  7. yuwenmemon commented on Apr 24, 2025

    @yuwenmemon
    Contributor

    @nlemma, you said this was a new feature you were testing. What PR were you testing when you ran into this issue? Moving forward, can you please be sure to always include that detail in your issues when that is the case?

  8. nlemma commented on Apr 24, 2025

    @nlemma
    Author

    @yuwenmemon thanks for pointing that out, I've updated the OP to include the PR that introduced the feature. Will make sure to include that detail in future reports.

  9. 14 remaining items

  10. trjExpensify commented on Apr 24, 2025

    @trjExpensify
    Contributor

    Ahhh, I see it now. Cool. Mhm yeah, not sure what's bust there. Even in the other "broken" one-expense report table views for a one-expense expenseReport or one-expense iouReport, we're still showing the transaction details when opened. So it does look like a bug specific to the sendMoney flow.

    2025-04-24_19-56-45.mp4
  11. changed the title [-][$250] Expense - Paid system message thread opens when opening expense from "Pay someone"[/-] [+][Better Expense Report View] [$250] Expense - Paid system message thread opens when opening expense from "Pay someone"[/+] on Apr 24, 2025
  12. melvin-bot commented on Apr 24, 2025

    @melvin-bot

    ❌ There was an error making the offer to @allgandalf for the Contributor role. The BZ member will need to manually hire the contributor.

  13. mountiny commented on Apr 24, 2025

    @mountiny
    Contributor

    Thanks for handling, if you want, feel free to reassign to me @yuwenmemon as part of the project

  14. moved this to Second Cohort - CRITICAL in [#whatsnext] #migrateon Apr 25, 2025
  15. changed the title [-][Better Expense Report View] [$250] Expense - Paid system message thread opens when opening expense from "Pay someone"[/-] [+][HOLD https://github.com/Expensify/App/pull/60884] [Better Expense Report View] [$250] Expense - Paid system message thread opens when opening expense from "Pay someone"[/+] on Apr 25, 2025
  16. mountiny commented on Apr 25, 2025

    @mountiny
    Contributor

    This seems to be specific to the Send Money flow and its possible that was not tested thoroughly. I think this might go away after #60884 is merged. @DylanDylann mind testing it on the PR? thanks!

  17. melvin-bot commented on Apr 28, 2025

    @melvin-bot

    @Kicu, @yuwenmemon, @VictoriaExpensify, @allgandalf Whoops! This issue is 2 days overdue. Let's get this updated quick!

  18. trjExpensify commented on Apr 29, 2025

    @trjExpensify
    Contributor

    Confirmed this is resolved on staging by #60884, closing it out!

    2025-04-29_13-35-19.mp4
  19. moved this from Second Cohort - CRITICAL to Done in [#whatsnext] #migrateon Apr 29, 2025
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.DailyKSv2EngineeringExternalAdded to denote the issue can be worked on by a contributor

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions