Skip to content

Home- Expense opens in transaction thread after switching to table view and reopening expense #104649

Closed
Closed
Home- Expense opens in transaction thread after switching to table view and reopening expense#104649
Assignees
Beamanatorlakchotemountinydaledah
Labels
BugSomething is broken. Auto assigns a BugZero manager.DeployBlockerCashThis issue or pull request should block deploymentEngineeringHourlyKSv2ReviewingHas a PR in review

Description

@applause-bot
applause-bot
bot
opened on Oct 21, 2026

If you haven’t already, check out our contributing guidelines for onboarding. To join our Slack channel, fill out this form.

Version Number: 9.5.16-0
Reproducible in staging?: Yes
Reproducible in production?: N/A - new feature, doesn't exist in prod
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #103703
Email or phone of affected tester (no customers): [email protected]
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Mac 26.5 / Chrome
App Component: Money Requests

Action Performed:

  1. Go to staging.new.expensify.com
  2. Go to workspace chat.
  3. Create an expense.
  4. Go to Home.
  5. Open the expense from Recently added section.
  6. Click More > Switch to table view.
    → Expense opens in table view.
  7. Close and reopen the same expense.
    → Expense opens in transaction thread.

Expected Result:

In Step 7, after switching to table view and reopening the expense, expense will remain in table view.

Actual Result:

In Step 7, after switching to table view and reopening the expense, expense opens in transaction thread.

Workaround:

Unknown

Platforms:

  • Android: App
  • Android: mWeb Chrome
  • iOS: App
  • iOS: mWeb Safari
  • iOS: mWeb Chrome
  • Windows: Chrome
  • MacOS: Chrome Safari

Screenshots/Videos

Bug7292527_1792613155326.6.mp4

View all open jobs on GitHub

Applause Internal Information
Exported by: Svetlana Lazutkina
Bug ID: 7292527

Activity

  1. applause-bot
    added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    on Oct 21, 2026
  2. gleitebr
    added this to #expensify-bugson Oct 21, 2026

  3. applause-bot commented on Oct 21, 2026

    @applause-bot
    applause-botBot
    on Oct 21, 2026
    Author

    While Applause doesn't embed attachments for this bug, here are the links for quick view:
    https://platform.applause.com/services/links/v1/external/1800b03b454a1c81cd9193678b72a45b0e5ad0248ad3ee8f030ed562f1a499b8

  4. melvin-bot
    assigned
    Beamanator
    on Oct 21, 2026

  5. melvin-bot commented on Oct 21, 2026

    @melvin-bot
    melvin-botBot
    on Oct 21, 2026 – with Melvin Bot

    You have been assigned to this deploy blocker because you recently merged this PR: #103703

  6. melvin-bot
    assigned
    mountiny
    ,
    lakchote
    and
    daledah
    on Oct 21, 2026

  7. melvin-bot commented on Oct 21, 2026

    @melvin-bot
    melvin-botBot
    on Oct 21, 2026 – with Melvin Bot

    @Beamanator @mountiny @lakchote @daledah you have been assigned to this deploy blocker because you reviewed the offending PR: #103703

  8. melvin-bot commented on Oct 21, 2026

    @melvin-bot
    melvin-botBot
    on Oct 21, 2026 – with Melvin Bot

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

  9. github-actions
    added
    Engineering
    HourlyKSv2
    on Oct 21, 2026

  10. github-actions commented on Oct 21, 2026

    @github-actions
    github-actionsBot
    on Oct 21, 2026 – with 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.

  11. MelvinBot commented on Oct 21, 2026

    @MelvinBot
    MelvinBot
    on Oct 21, 2026
    Contributor

    Deploy Blocker Analysis

    Causing PR: Reapply "Add a More menu option to switch single-expense reports between expense view and table view" (high confidence). The auto-assignment was correct.

    Root cause: The PR added !shouldUseTableViewForSingleExpense to the thread-to-report redirect in OneTransactionThreadRedirectHandler.tsx:96-97. Recently added always opens the expense's transaction thread. In expense view, that thread redirects to the parent report. In table view, the redirect never fires, so the user stays on the thread.

    This is intended behavior, not a broken build. The PR added it on purpose, so tapping a table row opens the expense thread. A unit test locks it in: keeps the thread route when the user views single-expense reports in the table view. The feature isn't in production, and only users who turn on table view see this.

    Recommendation: Demote after a product owner on [$175] Add a More menu option to switch single-expense reports between expense view and table view confirms the expected behavior. If product wants the report to open, roll forward with the fix below. Don't revert. The feature was already reverted once.

    Roll-forward fix (if product wants the report in table view)

    Only skip the redirect in table view when the thread was opened from its own report. That's the table-row case, which passes the report as backTo (useNavigateToTransactionThread.ts:67-73).

    1. Move the isBackToParentReport check (OneTransactionThreadRedirectHandler.tsx:106) out of the effect, above shouldRedirectToParentReport.
    2. Replace !shouldUseTableViewForSingleExpense with !(shouldUseTableViewForSingleExpense && isBackToParentReport).
    3. Update the existing test, and add one for a backTo that isn't the parent report (for example, Home).

    Result: a row tap in table view still opens the thread. Recently added (backTo=home) and other entry points redirect to the report, which then shows in table view.

    Investigation details

    Next Steps: Reply with @MelvinBot implement this to create a draft PR with the roll-forward fix, or @MelvinBot <your feedback> to refine this analysis.

    view run

  12. melvin-bot
    added
    ReviewingHas a PR in review
    on Oct 21, 2026

  13. m-natarajan commented on Oct 22, 2026

    @m-natarajan
    m-natarajan
    on Oct 22, 2026

    Chrome / v9.5.16-1
    No Switch to table view option

    bandicam.2026-10-22.16-14-59-893.mp4

  14. Beamanator commented on Oct 22, 2026

    @Beamanator
    Beamanator
    on Oct 22, 2026
    Contributor

    thanks! closing!

  15. Beamanator
    closed this as completedon Oct 22, 2026
  16. github-project-automation
    moved this to Done in #expensify-bugson Oct 22, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

BugSomething is broken. Auto assigns a BugZero manager.DeployBlockerCashThis issue or pull request should block deploymentEngineeringHourlyKSv2ReviewingHas a PR in review

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions