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-06-25] [Hold for https://github.com/Expensify/App/pull/86283][$125] “Reimbursable” column width is wider than necessary on report page #82667
Version Number: 9.3.20-5 Reproducible in staging?: Y Reproducible in production?: Y If this was caught during regression testing, add the test name, ID and link from BrowserStack: Email or phone of affected tester (no customers): Logs:https://stackoverflow.com/c/expensify/questions/4856 Expensify/Expensify Issue URL: Issue reported by:@shawnborton Slack conversation (hyperlinked to channel name): #Expensify Bugs
Action Performed:
Open a report with multiple expenses
View the expense table
Observe the width of the Reimbursable column
Expected Result:
The Reimbursable column should use a fixed width.
Width should be just wide enough to comfortably fit the word “Reimbursable” (header) and values “Yes” / “No”.
The column should not occupy unnecessary horizontal space.
Actual Result:
The Reimbursable column is wider than needed.
It consumes more horizontal space than its content requires.
Workaround:
Unknown
Platforms:
Select the officially supported platforms where the issue was reproduced:
Please re-state the problem that we are trying to solve in this issue.
The "Reimbursable" (and "Billable") column on the report page is wider than necessary — it uses a fixed width of 92px, which is more space than required to display the column header text or the "Yes"/"No" cell values, wasting horizontal space on the report table.
What is the root cause of that problem?
The root cause is in the getReportTableColumnStyles function in src/styles/utils/index.ts (lines 1812–1814), where both the REIMBURSABLE and BILLABLE columns are assigned a fixed width of variables.w92 (92px):
92px is larger than necessary for columns whose content is limited to the header label "Reimbursable"/"Billable" and the cell values "Yes" or "No". For comparison, date columns (Submitted, Approved, Posted, Exported) already use variables.w72 (72px) in their narrow state and render comfortably at that width.
What changes do you think we should make in order to solve the problem?
This reduces the column width from 92px to 72px, reclaiming ~20px of horizontal space per column. The w72 value is already defined in src/styles/variables.ts (line 351) and is a proven width for short-text columns elsewhere in the codebase. After making this change, visual testing across platforms and locales should confirm the header text fits comfortably — if a particular locale's translation of "Reimbursable" is longer, the value can be bumped to w80 (80px), which still improves on the current 92px.
What alternative solutions did you explore? (Optional)
A narrower value such as w60 was considered but may be too tight for the "Reimbursable" header text in some locales. A more flexible approach using flex-based sizing instead of a fixed pixel width was also considered, but staying consistent with the fixed-width pattern used by all other columns in this table is preferable to avoid layout inconsistencies.
Please re-state the problem that we are trying to solve in this issue.
When a user opens a report with multiple expenses and views the expense table, the Reimbursable column is wider than needed. It consumes more horizontal space than its content requires (header “Reimbursable” and cell values “Yes” / “No”).
The Reimbursable column is wider than needed and consumes more horizontal space than its content requires.
What is the root cause of that problem?
The Reimbursable (and Billable) column width is set to variables.w92 (92px) in the report table column styles. The same 92 px value is used in getTableMinWidth when computing the minimum table width. This fixed width is larger than necessary for the short header and “Yes”/“No” values, so the column takes more horizontal space than needed.
Relevant behavior (permalink = link to code on main):
The Reimbursable and Billable columns are assigned a width of variables.w92 (92px) in getReportTableColumnStyles.
What changes do you think we should make in order to solve the problem?
Use a smaller fixed width for the Reimbursable and Billable columns so the column is just wide enough to fit the header and “Yes”/“No” values. The codebase already defines variables.w80 (80px), which is used for other compact columns (e.g. ACTION). Use variables.w80 (80px) for Reimbursable and Billable in both:
Style utils (App/src/styles/utils/index.ts) – In getReportTableColumnStyles, for CONST.SEARCH.TABLE_COLUMNS.REIMBURSABLE and CONST.SEARCH.TABLE_COLUMNS.BILLABLE, set the width to variables.w80 instead of variables.w92.
SearchUIUtils (App/src/libs/SearchUIUtils.ts) – In getTableMinWidth, when the column is Reimbursable or Billable, add 80 to the minimum width instead of 92 so the table’s minimum width calculation stays in sync with the column width.
changed the title [-]“Reimbursable” column width is wider than necessary on report page[/-][+][$125] “Reimbursable” column width is wider than necessary on report page[/+]on Feb 17, 2026
If there are posts on the PR or issue that reference a regression or deploy blocker, C+ posts on the issue and confirms regression (which will reduce pay by 50%) or provides reasoning why they shouldn’t be considered. If the C+ doesn’t update the issue, the contributor manager making the payment will assume any mention of a regression or deploy blockers reduces the issue amount.
@hungvu193 if you were the C+ responsible for a regression and you chose to hand off that work, I'm unsure if you're due payment cuz we'd be paying a premium for others to fix the regression.
@hungvu193 if you were the C+ responsible for a regression and you chose to hald off that work, I'm unsure if you're due payment cuz we'd be paying a premium for others to fix the regression.
Activity
melvin-bot commentedon Feb 17, 2026
Triggered auto assignment to Contributor-plus team member for initial proposal review - @hungvu193 (
External)melvin-bot commentedon Feb 17, 2026
Triggered auto assignment to @johncschuster (
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.melvin-bot commentedon Feb 17, 2026
Unable to auto-create job on Upwork. The BZ team member should create it manually for this issue.
twilight2294 commentedon Feb 17, 2026
Proposal
Please re-state the problem that we are trying to solve in this issue.
The "Reimbursable" (and "Billable") column on the report page is wider than necessary — it uses a fixed width of 92px, which is more space than required to display the column header text or the "Yes"/"No" cell values, wasting horizontal space on the report table.
What is the root cause of that problem?
The root cause is in the
getReportTableColumnStylesfunction insrc/styles/utils/index.ts(lines 1812–1814), where both theREIMBURSABLEandBILLABLEcolumns are assigned a fixed width ofvariables.w92(92px):This fixed width is applied to both the table header cell in
src/components/SelectionListWithSections/SortableTableHeader.tsx(lines 82–93) and the transaction row cell insrc/components/TransactionItemRow/index.tsx(lines 381–388), both of which callStyleUtils.getReportTableColumnStyles(CONST.SEARCH.TABLE_COLUMNS.REIMBURSABLE).92px is larger than necessary for columns whose content is limited to the header label "Reimbursable"/"Billable" and the cell values "Yes" or "No". For comparison, date columns (Submitted, Approved, Posted, Exported) already use
variables.w72(72px) in their narrow state and render comfortably at that width.What changes do you think we should make in order to solve the problem?
Change the width of the
REIMBURSABLEandBILLABLEcolumns fromvariables.w92tovariables.w72insrc/styles/utils/index.ts(lines 1812–1814):This reduces the column width from 92px to 72px, reclaiming ~20px of horizontal space per column. The
w72value is already defined insrc/styles/variables.ts(line 351) and is a proven width for short-text columns elsewhere in the codebase. After making this change, visual testing across platforms and locales should confirm the header text fits comfortably — if a particular locale's translation of "Reimbursable" is longer, the value can be bumped tow80(80px), which still improves on the current 92px.What alternative solutions did you explore? (Optional)
A narrower value such as
w60was considered but may be too tight for the "Reimbursable" header text in some locales. A more flexible approach usingflex-based sizing instead of a fixed pixel width was also considered, but staying consistent with the fixed-width pattern used by all other columns in this table is preferable to avoid layout inconsistencies.abbasifaizan70 commentedon Feb 17, 2026
Proposal
Please re-state the problem that we are trying to solve in this issue.
When a user opens a report with multiple expenses and views the expense table, the Reimbursable column is wider than needed. It consumes more horizontal space than its content requires (header “Reimbursable” and cell values “Yes” / “No”).
The Reimbursable column is wider than needed and consumes more horizontal space than its content requires.
What is the root cause of that problem?
The Reimbursable (and Billable) column width is set to
variables.w92(92px) in the report table column styles. The same 92 px value is used ingetTableMinWidthwhen computing the minimum table width. This fixed width is larger than necessary for the short header and “Yes”/“No” values, so the column takes more horizontal space than needed.Relevant behavior (permalink = link to code on
main):The Reimbursable and Billable columns are assigned a width of
variables.w92(92px) ingetReportTableColumnStyles.App/src/styles/utils/index.ts
Lines 1811 to 1815 in 0ad75d6
getTableMinWidthadds 92px to the minimum width for each Reimbursable or Billable column, matching the same value.App/src/libs/SearchUIUtils.ts
Lines 4576 to 4584 in 0ad75d6
What changes do you think we should make in order to solve the problem?
Use a smaller fixed width for the Reimbursable and Billable columns so the column is just wide enough to fit the header and “Yes”/“No” values. The codebase already defines
variables.w80(80px), which is used for other compact columns (e.g. ACTION). Usevariables.w80(80px) for Reimbursable and Billable in both:Style utils (
App/src/styles/utils/index.ts) – IngetReportTableColumnStyles, forCONST.SEARCH.TABLE_COLUMNS.REIMBURSABLEandCONST.SEARCH.TABLE_COLUMNS.BILLABLE, set the width tovariables.w80instead ofvariables.w92.SearchUIUtils (
App/src/libs/SearchUIUtils.ts) – IngetTableMinWidth, when the column is Reimbursable or Billable, add 80 to the minimum width instead of 92 so the table’s minimum width calculation stays in sync with the column width.Solution – new code (git diff):
[-]“Reimbursable” column width is wider than necessary on report page[/-][+][$125] “Reimbursable” column width is wider than necessary on report page[/+]melvin-bot commentedon Feb 17, 2026
97 remaining items
mallenexpensify commentedon Jun 27, 2026
@Krishna2323 @hungvu193 once Melv is finished above, please comment on the DBs mentioned. From the C+ doc
@hungvu193 if you were the C+ responsible for a regression and you chose to hand off that work, I'm unsure if you're due payment cuz we'd be paying a premium for others to fix the regression.
hungvu193 commentedon Jun 28, 2026
Yeah. I think that makes sense 😄.
Krishna2323 commentedon Jun 30, 2026
@mallenexpensify, here's a quick payment breakdown:
Confirming that #83124 caused the #85655 regression. #93148 did not introduce any new regressions. We don't need a checklist here.
mallenexpensify commentedon Jul 1, 2026
Payment Summary
Contributor: @twilight2294 paid $75 via Upwork
Contributor+: @Krishna2323 due $125 via NewDot
@twilight2294 can you please accept the job below? Please reply here and tag me once you have.
https://www.upwork.com/jobs/~022072402115441515695
twilight2294 commentedon Jul 6, 2026
done @mallenexpensify
mallenexpensify commentedon Jul 6, 2026
@twilight2294 paid, summary updated above. Thx.
laurenreidexpensify commentedon Jul 24, 2026
$125 approved for @Krishna2323