Skip to content

[Due for payment 2026-11-10] Web - Report - Report table header is larger than rest of the table after merging reports. #103719

Closed

Description

@applause-bot

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.7-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #101034
Email or phone of affected tester (no customers): applausetester+ib0099@applause.expensifail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Windows 11 / Chrome
App Component: Money Requests

Action Performed:

Prerequisite: Use an expensifail account.
Prerequisite 2: Account has a workspace.

  1. Open the staging.new.expensify.com website.
  2. Navigate to workspace chat.
  3. Create two manual expenses on two different reports.
  4. Navigate to "Spend" > "Reports"
  5. Select both reports > "Merge Reports"
  6. Once on merge RHP, refresh the page.
  7. Select one of the reports > "Confirm"
  8. Once you land on report, note that table header is larger than the rest of the report.

Expected Result:

After merging reports, table header should remain with the same size and large as the rest of the report.

Actual Result:

After merging reports, table header is displayed larger than the rest of the report. It returns to normal large after closing and reopening report.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7283151_1791643976791.Reports_Merge.mp4

View all open jobs on GitHub

Applause Internal Information
Exported by: Julia Ponikarchuk
Bug ID: 7283151

Issue OwnerCurrent Issue Owner: @dmkt9

Activity

  1. added
    BugSomething is broken. Auto assigns a BugZero manager.
    on Oct 12, 2026
  2. applause-bot commented on Oct 12, 2026

    @applause-bot
    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/fb375f72f32c0bf97c7662cde34aa2fa0d42c5119fe577bb5d874bc3f3d23916

  3. melvin-bot commented on Oct 12, 2026

    @melvin-bot

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

  4. melvin-bot commented on Oct 12, 2026

    @melvin-bot

    @Gonals @situchan you have been assigned to this deploy blocker because you reviewed the offending PR: #101034

  5. melvin-bot commented on Oct 12, 2026

    @melvin-bot

    @dmkt9 you have been assigned to this deploy blocker because you authored the offending PR: #101034

  6. melvin-bot commented on Oct 12, 2026

    @melvin-bot

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

  7. github-actions commented on Oct 12, 2026

    @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.
  8. MelvinBot commented on Oct 12, 2026

    @MelvinBot
    Contributor

    Deploy Blocker Analysis

    Likely cause (medium confidence): Fix regressions with merging reports, by dmkt9.

    Recommendation: Don't revert. Fix forward, or demote.

    • A revert would bring back the regressions that PR fixed, including the empty merge page after a refresh.
    • Production doesn't show this glitch only because the flow can't be completed there after a refresh.
    • The bug is cosmetic and behind the REPORT_MERGE beta. It needs a mid-flow refresh, and it goes away when you reopen the report.
    Investigation details

    Why this PR

    What is not confirmed

    • Column math is not the cause. The header and rows get the same columns from one useMoneyRequestReportColumns call (MoneyRequestReportTransactionList.tsx:251-252). They also use the same horizontal margin.
    • Stale row width is a guess. The rows may keep the width they had while the RHP was still expanding. But FlashList re-measures when its container resizes, so this isn't proven.
    • Not reproduced live. The test session didn't finish onboarding, and Merge Reports needs the REPORT_MERGE beta.

    Suggested next steps for dmkt9

    1. Reproduce with and without the refresh. Compare the RHP width and the navigation state when the report mounts.
    2. As a first test, remove the new backTo at SearchReportsMergeReports.tsx:209 and useSearchBulkActions.ts:2939.
    3. If the rows keep a stale width, re-key the list or force a re-layout after the RHP finishes expanding.

    Next Steps: Reply with @MelvinBot <your feedback> to refine this analysis.


    view run

  9. 22 remaining items

  10. melvin-bot commented on Nov 9, 2026

    @melvin-bot

    Payment Summary

    Resolving PRs:

    BugZero Checklist (@mallenexpensify)

    • I have confirmed assignees, roles, and Upwork contracts look correct
    • I have paid out Upwork contracts / manual NewDot requests
    • [BugZero Assignee] I have created a GH issue for creating/updating the regression test once above steps have been agreed upon
  11. situchan commented on Nov 11, 2026

    @situchan
    Contributor

    Contributor+ Checklist:

    • [Contributor] The offending PR and associated issue have been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.

      Link to the comment on the PR: N/A. The root cause existed in production for long time
      Link to the comment on the Issue:

    • [Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.

      Link to discussion:

    • [Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.

    Regression Test Proposal

    Test:

    1. Open the app in a desktop web browser.
    2. Submit at least two expenses to a report.
    3. Go to Spend > Reports.
    4. Open the report.
    5. Verify that the comment loading state appears without displaying a scrollbar. After the loading state disappears, verify that the report table header remains in the same position.

    Do we agree 👍 or 👎

  12. situchan commented on Nov 11, 2026

    @situchan
    Contributor

    This is not a regression from #101034.
    #103719 (comment), #103719 (comment)

  13. melvin-bot commented on Nov 12, 2026

    @melvin-bot

    @mallenexpensify Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

  14. mallenexpensify commented on Nov 13, 2026

    @mallenexpensify
    Contributor

    Claude posting on behalf of Matt:

    Your call. Job price: $175 (standard, no Help Wanted, assigned 2026-10-12).

    • dmkt9 (Contributor): 100% if not a regression, 0% if it is, via NewDot
    • situchan (C+): 100% if not a regression, 0% if it is, via NewDot

    The BrowserStack field names #101034. dmkt9 wrote it and situchan approved it. This issue was created 2026-10-12, before #101034 reached production on 2026-10-13. That is inside the regression window.

    situchan says it is not a regression: comment

    Next: decide on the regression. Then press Caps+Y and pay.

    Evidence
    • C+ checklist, with test steps: comment
    • TestRail case: none yet
    • Resolving PR: #104066 by dmkt9, merged 2026-11-02, approved by Gonals, garrettmknight, situchan. No revert.
    • Offending PR: #101034 by dmkt9, approved by Gonals, situchan. Merged 2026-10-09, production 2026-10-13, window ended 2026-10-20.
    • Test videos: author 1/5, C+ 1/5.

    PAYPREP v1

  15. mallenexpensify commented on Nov 13, 2026

    @mallenexpensify
    Contributor

    Payment Summary

    Contributor: @dmkt9 paid $175 via Upwork
    Contributor+: @situchan due $175 via NewDot

    @dmkt9 can you please accept the job below? Please reply here and tag me once you have.
    https://www.upwork.com/jobs/~022121381504047545293

  16. dmkt9 commented on Nov 16, 2026

    @dmkt9
    Contributor

    @dmkt9 can you please accept the job below? Please reply here and tag me once you have.

    @mallenexpensify Thanks. I've accepted the offer

  17. mallenexpensify commented on Nov 16, 2026

    @mallenexpensify
    Contributor

    @dmkt9 paid, summary updated above. Thx.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionBugSomething is broken. Auto assigns a BugZero manager.DailyKSv2Engineering

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions