Skip to content

Reports - Individual expense row opens expense report instead of transaction thread #63461

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.59-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: #62080
Email or phone of affected tester (no customers): oijnonjoijnionjoi@gmail.com
Issue reported by: Applause Internal Team
Device used: Mac 15.4 / Chrome
App Component: Search

Action Performed:

  1. Go to staging.new.expensify.com
  2. Go to workspace chat.
  3. Submit two expenses to the workspace chat.
  4. Click Submit on the expense preview.
  5. Go to Reports.
  6. Click on any of the paid expenses.

Expected Result:

Transaction thread will open (production behavior).

Actual Result:

The expense report opens.

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

Bug6850736_1749056575347.20250605_005111.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.
    on Jun 4, 2025
  2. melvin-bot commented on Jun 4, 2025

    @melvin-bot

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

  3. melvin-bot commented on Jun 4, 2025

    @melvin-bot

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

  4. melvin-bot commented on Jun 4, 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.

  5. github-actions commented on Jun 4, 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 Jun 4, 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. 1 remaining item

  8. thienlnam commented on Jun 4, 2025

    @thienlnam
    Contributor

    I think this might actually be intentional since we're no longer creating the expense thread from #62080

    Can you confirm @VickyStash / @iwiznia?

  9. VickyStash commented on Jun 4, 2025

    @VickyStash
    Contributor

    Hi there 👋 I've checked and it looks like something we need to fix!
    To do that, we need to update this method:

    const openReportInRHP = (transactionItem: TransactionListItemType) => {

    to include these updates.

    I can prepare a PR tomorrow morning!

  10. thienlnam commented on Jun 4, 2025

    @thienlnam
    Contributor

    That would be great, thanks!

  11. sakluger commented on Jun 4, 2025

    @sakluger
    Contributor

    Hey @thienlnam, is this actually related to the PR (#62080) for #58828?

  12. VictoriaExpensify commented on Jun 5, 2025

    @VictoriaExpensify
    Contributor

    Waiting for a response on the above

  13. VickyStash commented on Jun 5, 2025

    @VickyStash
    Contributor

    Hey @thienlnam, is this actually related to the PR (#62080) for #58828?

    Yes, it's related to this PR!

  14. amyevans commented on Jun 5, 2025

    @amyevans
    Contributor

    Reverting #62080 in #63542

  15. amyevans commented on Jun 5, 2025

    @amyevans
    Contributor
  16. IuliiaHerets commented on Jun 5, 2025

    @IuliiaHerets

    @amyevans Issue is not reproducible on the build 9.1.59-7 Windows10/Chrome

    Recording.3223.mp4
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