Skip to content

[held #45203] [$250] Search - System message thread opens when opening from Search when system message has reply #44590

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.0-3.0
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Issue reported by: Applause - Internal Team

Issue found when executing PR #43742

Action Performed:

  1. Go to staging.new.expensify.com/
  2. Go to FAB > Pay someone
  3. Enter amount, select a user and pay them
  4. Go to transaction thrad
  5. Right click on the paid system message > Reply in thread
  6. Send a reply in thread
  7. Go to Search
  8. Open the expense sent previously

Expected Result:

Transaction thread will open

Actual Result:

System message thread opens when opening from Search when there is reply in system message

Workaround:

Unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

  • Android: Native
  • Android: mWeb Chrome
  • iOS: Native
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence

Bug6526871_1719533132122.20240628_080147.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~019c1a520581844a96
  • Upwork Job ID: 1810271704827245079
  • Last Price Increase: 2024-09-02
Issue OwnerCurrent Issue Owner: @

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    DeployBlockerIndicates it should block deploying the API
    on Jun 28, 2024
  2. melvin-bot commented on Jun 28, 2024

    @melvin-bot

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

  3. github-actions commented on Jun 28, 2024

    @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.
  4. lanitochka17 commented on Jun 28, 2024

    @lanitochka17
    Author

    @hayata-suenaga 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

  5. lanitochka17 commented on Jun 28, 2024

    @lanitochka17
    Author

    We think that this bug might be related to #wave-collect - Release 1

  6. added and removed
    DeployBlockerCashThis issue or pull request should block deployment
    DeployBlockerIndicates it should block deploying the API
    on Jun 28, 2024
  7. mountiny commented on Jun 28, 2024

    @mountiny
    Contributor

    This is not a blocker, but it's kind of an expected result of the one-transaction view design. In essence, an IOU action thread is a transaction thread, so replying to the report action in the thread is leaving a comment on the transaction thread.

    I think this is not a bug @lanitochka17

    @NikkiWines @trjExpensify to confirm, I am not sure what else we could do about this, but it's an edge case for Send Payment flow

  8. trjExpensify commented on Jun 28, 2024

    @trjExpensify
    Contributor
  9. 46 remaining items

  10. added
    BugSomething is broken. Auto assigns a BugZero manager.
    on Aug 2, 2024
  11. melvin-bot commented on Aug 2, 2024

    @melvin-bot

    Triggered auto assignment to @joekaufmanexpensify (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.

  12. joekaufmanexpensify commented on Aug 2, 2024

    @joekaufmanexpensify
    Contributor

    Still held on this issue

  13. melvin-bot commented on Aug 5, 2024

    @melvin-bot

    📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸

  14. melvin-bot commented on Aug 12, 2024

    @melvin-bot

    📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸

  15. joekaufmanexpensify commented on Aug 19, 2024

    @joekaufmanexpensify
    Contributor

    @getusha #45203 is closed now. Should we take this off hold now?

  16. melvin-bot commented on Aug 19, 2024

    @melvin-bot

    📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸

  17. mvtglobally commented on Aug 23, 2024

    @mvtglobally

    Issue not reproducible during KI retests. (First week)

  18. melvin-bot commented on Aug 26, 2024

    @melvin-bot

    📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸

  19. melvin-bot commented on Sep 2, 2024

    @melvin-bot

    📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸

  20. joekaufmanexpensify commented on Sep 2, 2024

    @joekaufmanexpensify
    Contributor

    Closing this as it's no longer reproducible.

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.EngineeringExternalAdded to denote the issue can be worked on by a contributorHelp WantedApply this label when an issue is open to proposals by contributorsMonthlyKSv2

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions