You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Due for payment 2026-11-10] Web - Report - Report table header is larger than rest of the table after merging reports. #103719
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.
Open the staging.new.expensify.com website.
Navigate to workspace chat.
Create two manual expenses on two different reports.
Navigate to "Spend" > "Reports"
Select both reports > "Merge Reports"
Once on merge RHP, refresh the page.
Select one of the reports > "Confirm"
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.
👋 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:
Identify the pull request that introduced this issue and revert it.
It makes the repro reachable. Before this PR, the merge page read the selection from in-memory search state. A refresh (step 6) cleared it, so Confirm (step 7) couldn't be used. The PR now stores the IDs in Onyx:
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
Reproduce with and without the refresh. Compare the RHP width and the navigation state when the report mounts.
[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:
Open the app in a desktop web browser.
Submit at least two expenses to a report.
Go to Spend > Reports.
Open the report.
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.
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.
Activity
applause-bot commentedon Oct 12, 2026
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
melvin-bot commentedon Oct 12, 2026
You have been assigned to this deploy blocker because you recently merged this PR: #101034
melvin-bot commentedon Oct 12, 2026
@Gonals @situchan you have been assigned to this deploy blocker because you reviewed the offending PR: #101034
melvin-bot commentedon Oct 12, 2026
@dmkt9 you have been assigned to this deploy blocker because you authored the offending PR: #101034
melvin-bot commentedon Oct 12, 2026
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon Oct 12, 2026
👋 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:
MelvinBot commentedon Oct 12, 2026
Deploy Blocker Analysis
Likely cause (medium confidence): Fix regressions with merging reports, by
dmkt9.Recommendation: Don't revert. Fix forward, or demote.
REPORT_MERGEbeta. It needs a mid-flow refresh, and it goes away when you reopen the report.Investigation details
Why this PR
src/components/Table/*, which the report transaction table doesn't use.SEARCH_MONEY_REQUEST_REPORTwithbackTo: Navigation.getActiveRoute(). That route opens in the super-wide RHP (WIDE_RIGHT_MODALS.ts:9).What is not confirmed
useMoneyRequestReportColumnscall (MoneyRequestReportTransactionList.tsx:251-252). They also use the same horizontal margin.REPORT_MERGEbeta.Suggested next steps for
dmkt9backToat SearchReportsMergeReports.tsx:209 and useSearchBulkActions.ts:2939.Next Steps: Reply with
@MelvinBot <your feedback>to refine this analysis.view run
22 remaining items
melvin-bot commentedon Nov 9, 2026
Payment Summary
Resolving PRs:
Fix report table header is larger than rest of the table #104066
Reviewer: @situchan owed $175 via NewDot
Assignee: @dmkt9 requires payment (Needs manual offer from BZ)
BugZero Checklist (@mallenexpensify)
situchan commentedon Nov 11, 2026
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:
Do we agree 👍 or 👎
situchan commentedon Nov 11, 2026
This is not a regression from #101034.
#103719 (comment), #103719 (comment)
melvin-bot commentedon Nov 12, 2026
@mallenexpensify Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!
mallenexpensify commentedon Nov 13, 2026
Claude posting on behalf of Matt:
Your call. Job price: $175 (standard, no Help Wanted, assigned 2026-10-12).
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
PAYPREP v1mallenexpensify commentedon Nov 13, 2026
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
dmkt9 commentedon Nov 16, 2026
@mallenexpensify Thanks. I've accepted the offer
mallenexpensify commentedon Nov 16, 2026
@dmkt9 paid, summary updated above. Thx.