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-05-13] [Due for payment 2026-05-12] Expense - Category, tag, tax, total column are not aligned correctly #89529
Version Number: 9.3.66-1 Reproducible in staging?: Yes Reproducible in production?: No If this was caught during regression testing, add the test name, ID and link from BrowserStack:#88296 Email or phone of affected tester (no customers):josdjnosdjionjsdonjisod@gmail.com Issue reported by: Applause Internal Team Bug source: Exploratory - Significant User Experience Deterioration Device used: Mac 26.2 / Chrome App Component: Money Requests
Action Performed:
Precondition:
Enable tag and taxes in workspace settings.
Go to staging.new.expensify.com
Go to workspace chat.
Create two expense with category, tag and tax.
Open the report.
Expected Result:
Category, tag and tax column will be aligned correctly.
Actual Result:
Category, tag and tax column are not aligned correctly.
Same issue also happens with Total column in IOU 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.
Classification: Frontend bug Causing PR: #88296 - "Update report details view to use compact desktop table styles" by @Krishna2323 (High confidence) Related Issues: #86203
Recommendation: REVERT
PR #88296 introduced a new shouldRemoveTotalColumnFlex flag and substantially reworked the table layout styles for the compact desktop report view. The column misalignment on MacOS/Chrome in staging (v9.3.66-1) directly matches the scope of changes in this PR — both the table header and the transaction rows were restyled, and any mismatch in how the column flex/width is applied between the header and rows would produce the misalignment seen in the screenshots.
Assigned: @Krishna2323 (PR author), @JS00001, @luacmartins, @situchan (approving reviewers) Labels: No label changes needed — DeployBlockerCash is correct (staging-only frontend bug in Expensify/App); DeployBlocker is not present and should not be added.
src/components/MoneyRequestReportView/MoneyRequestReportTransactionList.tsx — reworks the table header container styles and removes gap2 between grouped transactions
src/components/MoneyRequestReportView/MoneyRequestReportTransactionItem.tsx — passes shouldRemoveTotalColumnFlex to row items
src/components/TransactionItemRow/index.tsx — passes shouldRemoveTotalColumnFlex through to getReportTableColumnStyles for TOTAL_AMOUNT, TOTAL_PER_ATTENDEE, and ORIGINAL_AMOUNT columns
src/components/MoneyRequestReportView/MoneyRequestReportGroupHeader.tsx — reworks group header height and padding
Root Cause
The getReportTableColumnStyles function in src/styles/utils/index.ts at line 1929 applies flex1 to the total/amount columns unless shouldRemoveTotalColumnFlex is true. PR #88296 passes shouldRemoveTotalColumnFlex to the row items (MoneyRequestReportTransactionItem) and the table header (MoneyRequestReportTableHeader), removing the flex1 flex grow from those columns. However, the group header (MoneyRequestReportGroupHeader) does not receive this flag — meaning the group header row may lay out its columns at a different width than the data rows and the table header, producing the visible misalignment between category, tag, tax, and total columns.
Not seeing any differences between production and staging on my end. Going to keep closed for now, I'll let the PR author and reviewers confirm if we need to fix something else.
changed the title [-]Expense - Category, tag, tax, total column are not aligned correctly[/-][+][Due for payment 2026-05-12] Expense - Category, tag, tax, total column are not aligned correctly[/+]on May 5, 2026
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.3.66-7 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
@Krishna2323 / @situchan The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]
changed the title [-][Due for payment 2026-05-12] Expense - Category, tag, tax, total column are not aligned correctly[/-][+][Due for payment 2026-05-13] [Due for payment 2026-05-12] Expense - Category, tag, tax, total column are not aligned correctly[/+]on May 6, 2026
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.3.67-13 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
@Krishna2323 / @situchan The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]
Activity
melvin-bot commentedon May 4, 2026
You have been assigned to this deploy blocker because you recently merged this PR: #88296
melvin-bot commentedon May 4, 2026
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon May 4, 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:
JS00001 commentedon May 4, 2026
@Krishna2323 another blocker
OSBotify commentedon May 4, 2026
Investigation Summary
Classification: Frontend bug
Causing PR: #88296 - "Update report details view to use compact desktop table styles" by @Krishna2323 (High confidence)
Related Issues: #86203
Recommendation: REVERT
PR #88296 introduced a new
shouldRemoveTotalColumnFlexflag and substantially reworked the table layout styles for the compact desktop report view. The column misalignment on MacOS/Chrome in staging (v9.3.66-1) directly matches the scope of changes in this PR — both the table header and the transaction rows were restyled, and any mismatch in how the column flex/width is applied between the header and rows would produce the misalignment seen in the screenshots.Assigned: @Krishna2323 (PR author), @JS00001, @luacmartins, @situchan (approving reviewers)
Labels: No label changes needed —
DeployBlockerCashis correct (staging-only frontend bug inExpensify/App);DeployBlockeris not present and should not be added.Detailed Analysis
Evidence
pathandkeyPatternare next to each other #30 in the StagingDeployCash chronological order, merging on 2026-05-01 — well within this staging cycle.Verification
src/components/MoneyRequestReportView/MoneyRequestReportTransactionList.tsx— reworks the table header container styles and removesgap2between grouped transactionssrc/components/MoneyRequestReportView/MoneyRequestReportTableHeader.tsx— addsshouldRemoveTotalColumnFlexpropsrc/components/MoneyRequestReportView/MoneyRequestReportTransactionItem.tsx— passesshouldRemoveTotalColumnFlexto row itemssrc/components/TransactionItemRow/index.tsx— passesshouldRemoveTotalColumnFlexthrough togetReportTableColumnStylesfor TOTAL_AMOUNT, TOTAL_PER_ATTENDEE, and ORIGINAL_AMOUNT columnssrc/components/MoneyRequestReportView/MoneyRequestReportGroupHeader.tsx— reworks group header height and paddingRoot Cause
The
getReportTableColumnStylesfunction insrc/styles/utils/index.tsat line 1929 appliesflex1to the total/amount columns unlessshouldRemoveTotalColumnFlexis true. PR #88296 passesshouldRemoveTotalColumnFlexto the row items (MoneyRequestReportTransactionItem) and the table header (MoneyRequestReportTableHeader), removing theflex1flex grow from those columns. However, the group header (MoneyRequestReportGroupHeader) does not receive this flag — meaning the group header row may lay out its columns at a different width than the data rows and the table header, producing the visible misalignment between category, tag, tax, and total columns.4 remaining items
m-natarajan commentedon May 5, 2026
Issue is reproducible on Windows 11 / Chrome in v9.3.66-5, It's better than before.
francoisl commentedon May 5, 2026
Not seeing any differences between production and staging on my end. Going to keep closed for now, I'll let the PR author and reviewers confirm if we need to fix something else.
[-]Expense - Category, tag, tax, total column are not aligned correctly[/-][+][Due for payment 2026-05-12] Expense - Category, tag, tax, total column are not aligned correctly[/+]melvin-bot commentedon May 5, 2026
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon May 5, 2026
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.3.66-7 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
If no regressions arise, payment will be issued on 2026-05-12. 🎊
For reference, here are some details about the assignees on this issue:
melvin-bot commentedon May 5, 2026
@Krishna2323 / @situchan The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]
[-][Due for payment 2026-05-12] Expense - Category, tag, tax, total column are not aligned correctly[/-][+][Due for payment 2026-05-13] [Due for payment 2026-05-12] Expense - Category, tag, tax, total column are not aligned correctly[/+]melvin-bot commentedon May 6, 2026
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.3.67-13 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
If no regressions arise, payment will be issued on 2026-05-13. 🎊
For reference, here are some details about the assignees on this issue:
melvin-bot commentedon May 6, 2026
@Krishna2323 / @situchan The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]