Skip to content

Rename Search "Date" filter to "Created date" and column to "Created" for expense reports - #99216

Open
dilshodmackbook-sketch wants to merge 28 commits into
Expensify:mainfrom
dilshodmackbook-sketch:update/98148-created-date-labels
Open

Rename Search "Date" filter to "Created date" and column to "Created" for expense reports#99216
dilshodmackbook-sketch wants to merge 28 commits into
Expensify:mainfrom
dilshodmackbook-sketch:update/98148-created-date-labels

Conversation

@dilshodmackbook-sketch

@dilshodmackbook-sketch dilshodmackbook-sketch commented Aug 21, 2026

Copy link
Copy Markdown
Contributor

Explanation of Change

Renames the Search Date filter to Created date and the table column header to Created, scoped to the types whose date column is a non-editable created timestamp: type:expense-report and type:task. Every other type keeps Date: invoice, expense and trip render the editable transaction date, chat has no date column, and the opened single-report table plus every non-Search surface keep Date too.

The rename is gated on a single shared predicate (isCreatedDateType) reused at every label source: the column-header builders, getSearchColumnTranslationKey (Sort by / Edit columns / saved search / Export current view CSV) and the filter-menu label. The date column is widened to w80 (from w62) only for those types so the longer Created header doesn't clip against its active-sort caret. getTableMinWidth follows the actual rendered width of the fixed DATE cell (62, or 80 for the widened Created column) instead of the previous 48, which was stale drift from when the cell rendered at w52. The date: query key and sortBy wire value never change, so saved searches, deep links and optimistic rows keep working, so only visible labels move.

Update (per @trjExpensify + @FitseTLT): scope settled on the types whose date column is a non-editable created timestamp: expense-report and task. Invoice keeps Date because on NewDot its date column shows the editable transaction date, so Created would mislabel it.

Fixed Issues

$ #98148
PROPOSAL: #98148 (comment)

Tests

Rename applies to type:expense-report and type:task only (their date column is a non-editable created timestamp). expense, invoice, trip and chat keep Date everywhere, as does the opened single-report table and every non-Search surface.

A. Renamed types show Created / Created date (do this for BOTH Expense reports and Tasks)

  1. Open Search and switch the type to Expense reports, then repeat all of the below with type Tasks.
  2. Table column header reads Created (not Date), and the header is not clipped by its sort caret when you sort by it.
  3. Open the Filters bar → the date filter row label reads Created date. Apply a date filter and confirm the applied-filter chip in the filters bar reads Created date.
  4. Open the Sort by popup → the option reads Created. Select it, then reopen the Display popup and confirm the Sort by summary row reads Created.
  5. Open Edit columns → the column entry reads Created.
  6. Open the advanced filters Date subpage (Filters → Date) → the page title reads Created date.
  7. Export current view → open the CSV and confirm the exported column header reads Created.
  8. Save the current view (Save search) → open the saved search's applied-Displays list and confirm both Sort by and Columns show Created.

B. Untouched types keep Date

  1. Switch the type to Expenses, Invoices, Trips and Chats. For each, verify the column header (where present), Filters row, applied chip, Sort by, Edit columns, Export CSV and Save search all still read Date. (Chats has no date column - just verify no Created label appears anywhere for it.)
  2. Confirm column alignment is unchanged for Expenses, Invoices and Trips - header and rows line up as before (this PR must not widen those).

C. Opened single report + unrelated labels

  1. Open a single expense report → its transaction table header and its Columns menu both still read Date.
  2. Verify an unrelated Date label outside Search (e.g. the IOU/transaction date field) is unchanged.
  • Verify that no errors appear in the JS console

Offline tests

Same as Tests. This is a pure relabel with no API calls, so behavior is identical online and offline.

QA Steps

Same as Tests.

  • Verify that no errors appear in the JS console

PR Author Checklist

  • I linked the correct issue in the ### Fixed Issues section above
  • I wrote clear testing steps that cover the changes made in this PR
    • I added steps for local testing in the Tests section
    • I added steps for the expected offline behavior in the Offline steps section
    • I added steps for Staging and/or Production testing in the QA steps section
    • I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
    • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
    • I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
  • I included screenshots or videos for tests on all platforms
  • I ran the tests on all platforms & verified they passed on:
    • Android: Native
    • Android: mWeb Chrome
    • iOS: Native
    • iOS: mWeb Safari
    • MacOS: Chrome / Safari
  • I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
  • I followed proper code patterns (see Reviewing the code)
    • I verified that comments were added to code that is not self explanatory
    • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
    • I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
  • If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
  • I followed the guidelines as stated in the Review Guidelines
  • I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
  • If a new CSS style is added I verified that:
    • A similar style doesn't already exist
    • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))
  • If new assets were added or existing ones were modified, I verified that:
    • The assets are optimized and compressed (for SVG files, run npm run compress-svg)
    • The assets load correctly across all supported platforms.
  • If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
  • If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
  • If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
  • If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
  • If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
    • I verified that all the inputs inside a form are aligned with each other.
    • I added Design label and/or tagged @Expensify/design so the design team can review the changes.
  • I added unit tests for any new feature or bug fix in this PR to help automatically prevent regressions in this user flow.
  • If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native
Screen.Recording.2026-08-23.at.11.13.57.mov
Android: mWeb Chrome
PR99216_mWeb_responsive.mp4
iOS: Native
Screen.Recording.2026-08-23.at.12.03.23.mov
iOS: mWeb Safari
PR99216_mWeb_responsive.mp4
MacOS: Chrome / Safari
demo-video.mp4
Image

The type:expense table keeps the Date column header. The rename only applies to the report-style types.

Add dedicated search.filters.createdDate / search.filters.created keys
(all 11 locales), repoint FILTER_VIEW_MAP[DATE] and getSearchColumnTranslationKey
plus the three SearchTableHeader builders, and widen the narrow DATE column
(w62 -> w80) so "Created" + sort arrow fit without truncation.
common.date is left untouched.
getTableMinWidth adds 48 for DATE vs 72 for SUBMITTED/APPROVED/POSTED; the
"Created" header needs the same room, so bump it to 72 to keep the fixed
cell width (w80) and the horizontal-scroll min-width consistent.
Per the issue clarification, keep "Date" for type:expense (and the opened
single-report table) and show "Created"/"Created date" only for
type:expense-report. Thread the active Search type through the date label
sources (getSearchColumnTranslationKey, filter-menu labels via
getFilterViewLabelKey) and gate the DATE column widening on expense-report.
Asserts getSearchColumnTranslationKey, getFilterViewLabelKey, the expense
column builder and getTableMinWidth all keep "Date" for every type except
expense-report, so the scoped behavior can't silently regress to all types.
…stay Date)

Per the team clarification (invoice is treated like a report, trip is an
expense), the report-style rename now covers type:invoice as well as
type:expense-report. Introduce an isCreatedDateType(type) predicate
(expense-report OR invoice) and use it at every date-label source:
getSearchColumnTranslationKey, getFilterViewLabelKey, getTableMinWidth,
the SortableTableHeader isDateColumnCreated prop, and getExpenseHeaders
(now type-aware so shared expense/trip/opened-report callers stay on Date).
…n misalignment)

The header/min-width for type:invoice now render the wider Created column,
but invoice results render through ExpenseFlatSearchView -> TransactionItemRow
(the same transaction-row path as expense), whose DATE cell was fixed at w62.
That left the invoice header at w80 while its rows stayed w62 -> misaligned
columns. Thread an isDateColumnCreated flag from ExpenseFlatSearchView (true
only for type:invoice) through TransactionListItem -> TransactionItemRow to the
DATE cell so rows match the header. The opened single-report table passes
nothing (defaults false), so it stays on the narrow Date column.
@melvin-bot

melvin-bot Bot commented Aug 21, 2026

Copy link
Copy Markdown

Hey, I noticed you changed src/languages/en.ts in a PR from a fork. For security reasons, translations are not generated automatically for PRs from forks.

If you want to automatically generate translations for other locales, an Expensify employee will have to:

  1. Look at the code and make sure there are no malicious changes.
  2. Run the Generate static translations GitHub workflow. If you have write access and the K2 extension, you can simply click: [this button]

Alternatively, if you are an external contributor, you can run the translation script locally with your own OpenAI API key. To learn more, try running:

npx bun ./scripts/generateTranslations.ts --help

Typically, you'd want to translate only what you changed by running npx bun ./scripts/generateTranslations.ts --compare-ref main

@melvin-bot
melvin-bot Bot requested review from arosiclair and joekaufmanexpensify and removed request for a team August 21, 2026 19:37
@melvin-bot

melvin-bot Bot commented Aug 21, 2026

Copy link
Copy Markdown

@arosiclair Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

@melvin-bot
melvin-bot Bot removed the request for review from a team August 21, 2026 19:38
@dilshodmackbook-sketch
dilshodmackbook-sketch marked this pull request as draft August 21, 2026 19:38

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: a205a3b023

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

Comment thread src/components/Search/SearchTableHeader.tsx Outdated
@codecov

codecov Bot commented Aug 21, 2026

Copy link
Copy Markdown

Codecov Report

❌ Looks like you've decreased code coverage for some files. Please write tests to increase, or at least maintain, the existing level of code coverage. See our documentation here for how to interpret this table.

Files with missing lines Coverage Δ
src/components/Search/SearchStaticList.tsx 40.81% <ø> (ø)
src/components/Search/SearchTableHeader.tsx 50.00% <100.00%> (+0.56%) ⬆️
src/components/Search/SortableTableHeader.tsx 43.47% <ø> (ø)
...ents/TransactionItemRow/TransactionItemRowWide.tsx 98.40% <100.00%> (+0.01%) ⬆️
src/components/TransactionItemRow/index.tsx 83.87% <ø> (ø)
src/hooks/useSearchBulkActions.ts 71.24% <100.00%> (ø)
...rsContentPage/SearchAdvancedFiltersContentBase.tsx 0.00% <ø> (ø)
src/pages/Search/SearchColumnsPage.tsx 0.00% <ø> (ø)
src/styles/utils/index.ts 58.66% <100.00%> (-0.19%) ⬇️
...components/Search/FilterDropdowns/DisplayPopup.tsx 0.00% <0.00%> (ø)
... and 8 more
... and 60 files with indirect coverage changes

Comment thread src/components/ColumnsSettingsList.tsx Outdated
Comment thread src/components/Search/SearchTableHeader.tsx Outdated
Comment thread src/components/TransactionItemRow/types.ts Outdated
Comment thread src/libs/SearchUIUtils.ts Outdated
Comment thread src/libs/SearchUIUtils.ts Outdated
Comment thread src/libs/SearchUIUtils.ts Outdated
Comment thread src/styles/utils/index.ts Outdated
@dilshodmackbook-sketch

Copy link
Copy Markdown
Contributor Author

@codex review

@dilshodmackbook-sketch

Copy link
Copy Markdown
Contributor Author

Quick heads-up @FitseTLT: the one red test (NextStepUtils > monthly on the 2nd) is a date-dependent flake, not something in this PR. It expects 2026-10-02 but gets 2026-09-02 because CI is running on the 2nd - it reproduces the same way on a clean checkout and this branch never touches NextStepUtils. It'll go green on a re-run any other day.

@FitseTLT

FitseTLT commented Sep 3, 2026

Copy link
Copy Markdown
Contributor

Reviewer Checklist

  • I have verified the author checklist is complete (all boxes are checked off).
  • I verified the correct issue is linked in the ### Fixed Issues section above
  • I verified testing steps are clear and they cover the changes made in this PR
    • I verified the steps for local testing are in the Tests section
    • I verified the steps for Staging and/or Production testing are in the QA steps section
    • I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
    • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
  • I checked that screenshots or videos are included for tests on all platforms
  • I included screenshots or videos for tests on all platforms
  • I verified that the composer does not automatically focus or open the keyboard on mobile unless explicitly intended. This includes checking that returning the app from the background does not unexpectedly open the keyboard.
  • I verified tests pass on all platforms & I tested again on:
    • Android: HybridApp
    • Android: mWeb Chrome
    • iOS: HybridApp
    • iOS: mWeb Safari
    • MacOS: Chrome / Safari
  • If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
  • I verified proper code patterns were followed (see Reviewing the code)
    • I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
    • I verified that comments were added to code that is not self explanatory
    • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
    • I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
  • If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
  • I verified that this PR follows the guidelines as stated in the Review Guidelines
  • I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
  • If a new component is created I verified that:
    • A similar component doesn't exist in the codebase
    • All props are defined accurately and each prop has a /** comment above it */
    • The file is named correctly
    • The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
    • The only data being stored in the state is data necessary for rendering and nothing else
    • For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
    • Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
    • All JSX used for rendering exists in the render method
    • The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
  • If any new file was added I verified that:
    • The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
  • If a new CSS style is added I verified that:
    • A similar style doesn't already exist
    • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG)
  • If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
  • If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
  • If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
  • If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
  • If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
    • I verified that all the inputs inside a form are aligned with each other.
    • I added Design label and/or tagged @Expensify/design so the design team can review the changes.
  • For any bug fix or new feature in this PR, I verified that sufficient unit tests are included to prevent regressions in this flow.
  • If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
  • I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: HybridApp
2026-09-03.17-55-04.mp4
Android: mWeb Chrome
2026-09-03.17-28-45.mp4
iOS: HybridApp
2026-09-03.20-53-48.mp4
iOS: mWeb Safari
2026-09-03.17-26-08.mp4
MacOS: Chrome / Safari
2026-09-03.17-24-01.mp4

@FitseTLT

FitseTLT commented Sep 3, 2026

Copy link
Copy Markdown
Contributor

@dilshodmackbook-sketch pls make the test steps cover all changes.

@FitseTLT

FitseTLT commented Sep 3, 2026

Copy link
Copy Markdown
Contributor

@MelvinBot @codex review

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review: Something went wrong. Try again later by commenting “@codex review”.

An unknown error occurred
ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

@FitseTLT

FitseTLT commented Sep 3, 2026

Copy link
Copy Markdown
Contributor

@codex review

@MelvinBot

MelvinBot commented Sep 3, 2026

Copy link
Copy Markdown
Contributor

Code review

Two things I'd change before merge — one is an actual layout regression on types this PR is supposed to leave alone, the other is ~4 files of prop plumbing that nothing reads. The label logic itself (isCreatedDateType + the two label sources) looks right and the scope matches what was agreed on the issue.

1. getTableMinWidth changes the date min-width for every type, not just the renamed ones 🔴

src/libs/SearchUIUtils.ts:7006

-            minWidth += 48;
+            minWidth += isCreatedDateType(type) ? 80 : 62;

The else branch went 48 → 62, so expense, invoice, trip and the opened report table all get +14px of min table width. That shifts the horizontal-scroll threshold on three call sites the PR claims it doesn't touch:

The PR description also says min-width goes 48 → 72, which matches neither branch of the shipped code. Please keep 48 in the else branch (or, if 62 is deliberate to match the real w62 cell, say so explicitly and fix the description).

2. isDateColumnCreated is threaded through TransactionListItem but never passed in 🔴

Four files exist only to forward a prop that is always undefined:

TransactionListItem's only render site is ExpenseFlatSearchView.tsx:106, which doesn't set it — and couldn't usefully, since that view is flat-expense only where isCreatedDateType is always false. This is the "unnecessary changes" FitseTLT flagged; dropping it removes 4 files from the diff. SearchStaticList, SearchTableHeader, TaskListItemRow and ExpenseReportListItemRowWide are the paths that actually feed the flag, and those all check out.

3. Don't hand-write the non-English strings 🟡

generateTranslations.yml runs on any src/languages/en.ts change and posts the generated locales as a patch. The 10 hand-written files bypass that, and two don't match their own siblings:

  • zh-hans: created: '创建' — neighbours use the completed aspect (已支付, 已导出, 已发布), so 已创建
  • ja: created: '作成' reads as the verb "create" rather than a column header

Suggest reverting the 10 locale files and letting Polyglot Parrot generate them from en.ts.

4. Minor

  • ColumnsSettingsList.tsx:76type?: SearchDataTypes; is the only prop in ColumnsSettingsListProps without a /** */ comment (every one of the other eight has one). A clearer name like searchType would also read better in a generic component.
  • CreatedDateScopedLabelsTest.ts:67-78 — the getTableMinWidth assertions are all relative (toBeGreaterThan, and toBe(expenseWidth) compares two values that both changed), which is why finding Some initial fixes and code style updates #1 passed CI. One absolute expectation would have caught it. Nothing covers getReportTableColumnStyles(DATE, {isDateColumnCreated}) either.

On FitseTLT's "make the test steps cover all changes"

The current Tests section covers the column header, filter row, Sort by, Edit columns and CSV export, but not these surfaces the diff also changes:

  1. Applied-filter chip in the filters bar (mapFiltersFormToLabelValueList) reads Created date on expense-report/task.
  2. Display popup's Sort by summary row (DisplayPopup) reads Created.
  3. Save search page's applied-Displays list (SearchSavePage) reads Created for both Sort by and Columns.
  4. The date filter subpage title (SearchAdvancedFiltersContentBase) reads Created date.
  5. The date column width — confirm the Created header isn't clipped by its sort caret on expense-report/task, and that expense/invoice/trip column alignment is unchanged.

Everything else looks good: the date: query key and sortBy wire value are untouched, getExpenseHeaders correctly keeps common.date for the shared expense/invoice/trip/opened-report path, and ReportDetailsColumnsPage correctly omits type so the opened report keeps Date. All checks are green apart from Check independent approval.


view run · no recording available

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review: Didn't find any major issues. Breezy!

Reviewed commit: 169528da86

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

@dilshodmackbook-sketch

Copy link
Copy Markdown
Contributor Author

Updated the Tests/QA steps to cover every surface the diff touches. Grouped by renamed types (expense-report + task) vs untouched types:

  • Section A walks the renamed types through all label sources: column header, filter row + applied chip, Sort by option + Display summary row, Edit columns, the Date subpage title, Export CSV, and Save search's Displays list. Plus the header-not-clipped-by-caret check.
  • Section B checks expense/invoice/trip/chat still read Date on every one of those surfaces, and that expense/invoice/trip column alignment is unchanged.
  • Section C keeps the opened single report (table + Columns menu) on Date and an unrelated Date label untouched.

@FitseTLT

FitseTLT commented Sep 3, 2026

Copy link
Copy Markdown
Contributor

Melvin comments @dilshodmackbook-sketch

- getTableMinWidth: restore the 48 budget for non-created DATE columns
  (expense/invoice/trip/opened report) and use 72 for the created column,
  matching the sibling date columns and the PR description. The previous
  62/80 shifted the horizontal-scroll threshold for types this PR leaves alone.
- Remove the isDateColumnCreated prop that was threaded through
  TransactionListItem but never passed in (invoice was descoped, and its only
  render site is flat-expense where the flag is always false). The live header
  path (SearchStaticList/SearchTableHeader -> SortableTableHeader/TransactionItemRow)
  is untouched.
- zh-hans/ja: match the completed aspect of the sibling status labels
  (已创建, 作成済み) instead of the bare verb form.
- ColumnsSettingsList: document the type prop (the only one without a comment).
- Tests: assert absolute getTableMinWidth values so a non-created regression
  can't pass, and cover getReportTableColumnStyles DATE cell width.
@dilshodmackbook-sketch

dilshodmackbook-sketch commented Sep 3, 2026

Copy link
Copy Markdown
Contributor Author

@FitseTLT thanks for the review. Addressed all four in 314ad30.

  1. Reverted the else branch back to 48 so expense, invoice, trip and the opened report keep their old scroll threshold. Created columns use 72 now, which matches the sibling Submitted/Approved/Posted budgets and the number in the PR description.

  2. Dropped the isDateColumnCreated forwarding from TransactionListItem (the 4 files), so they fall out of the diff. Left TransactionItemRow's prop in place since SearchStaticList still feeds it for the static expense-report/task rows, which is the path you called out as fine.

  3. Fixed the two that were off: zh-hans is 已创建 and ja is 作成済み now, matching the completed aspect of the neighbours. On a full revert: generateTranslations skips fork PRs, so it won't auto-generate here. I corrected these by hand for now, but happy to revert all ten and let you trigger Polyglot Parrot via workflow_dispatch if you'd rather have it generate them.

  4. Added the doc comment on the type prop. Also made the getTableMinWidth test assert absolute widths (that's how the 48 -> 62 slipped past) and added coverage for getReportTableColumnStyles on the DATE cell.

@FitseTLT

FitseTLT commented Sep 3, 2026

Copy link
Copy Markdown
Contributor

@dilshodmackbook-sketch from now on, do not apply translation by yourself just add the english translations and translation workflows will do the translation. @JS00001 pls run translations

Per review: don't hand-apply translations. The generateTranslations workflow
generates the non-English locales from the added en.ts keys (search.filters.created
and search.filters.createdDate).
@dilshodmackbook-sketch

Copy link
Copy Markdown
Contributor Author

Reverted the locales, en.ts only now. The red typecheck is just the missing generated keys, so it'll clear once the translation workflow runs. @JS00001 whenever you get a chance.

Per FitseTLT: DATE is fixed-width, so getTableMinWidth should budget its real
rendered width (w62, or w80 for the Created column), not the stale 48 (drift from
when the cell was w52) or the sibling columns' 72. Updated the PR description so
the min-width note matches the code.
@FitseTLT

FitseTLT commented Sep 3, 2026

Copy link
Copy Markdown
Contributor

@trjExpensify @sakluger Can u give us 👀 on the final result? I mean I want you to confirm the places where Created vs Created date is used. Ofcourse the changes only applied for expense-report and task.

2026-09-03.20-58-35.mp4

@dilshodmackbook-sketch

Copy link
Copy Markdown
Contributor Author

@FitseTLT sorry about this, you're right. I've been buried and running on barely any sleep the last couple of days, and I moved too fast reacting to Melvin instead of stopping to think it through. Restored the 80/62 widths and fixed the description to match. Won't push over your review like that again.

@trjExpensify

Copy link
Copy Markdown
Contributor

Can u give us 👀 on the final result? I mean I want you to confirm the places where Created vs Created date is used

@dubielzyk-expensify on this. I believe the intention of the suggestion was that everywhere but the Created column header of the table has the full Created date label. So does that mean the column selector here as well?

image

@dubielzyk-expensify

Copy link
Copy Markdown
Contributor

It wasn't my suggestion to change this, but yeah I think that makes sense. I think the only place we'd list Created is in the table header. Everywhere else should say Created date.

@trjExpensify

Copy link
Copy Markdown
Contributor

It wasn't my suggestion to change this, but yeah I think that makes sense

Oh, my bad. I thought it was! 😅

@dubielzyk-expensify

Copy link
Copy Markdown
Contributor

cc @sakluger as it's his baby :)

@dannymcclain

Copy link
Copy Markdown
Contributor

I think the only place we'd list Created is in the table header. Everywhere else should say Created date.

Not Jon or Sasha, but I totally agree with this.

@dilshodmackbook-sketch

Copy link
Copy Markdown
Contributor Author

@JS00001 quick bump, merged main so en.ts changed again, translations workflow needs another run to clear the typecheck whenever you're free

@OSBotify

Copy link
Copy Markdown
Contributor

🦜 Polyglot Parrot! 🦜

Squawk! Looks like you added some shiny new English strings. Allow me to parrot them back to you in other tongues:

View the translation diff
diff --git a/src/languages/de.ts b/src/languages/de.ts
index dd60e29e..ac50bf55 100644
--- a/src/languages/de.ts
+++ b/src/languages/de.ts
@@ -9568,6 +9568,8 @@ Fügen Sie weitere Ausgabelimits hinzu, um den Cashflow Ihres Unternehmens zu sc
                 [CONST.SEARCH.ACTION_FILTERS.EXPORT]: 'Export',
             },
             filterType: {label: 'Filtertyp', has: {positive: 'hat', negative: 'hat nicht'}, is: {positive: 'ist', negative: 'ist nicht'}},
+            created: 'Erstellt',
+            createdDate: 'Erstellungsdatum',
         },
         display: {
             label: 'Anzeige',
diff --git a/src/languages/el.ts b/src/languages/el.ts
index 99404a7e..cb3a2f67 100644
--- a/src/languages/el.ts
+++ b/src/languages/el.ts
@@ -9777,6 +9777,8 @@ ${reportName}`,
                 has: {positive: 'έχει', negative: 'δεν έχει'},
                 is: {positive: 'είναι', negative: 'δεν είναι'},
             },
+            created: 'Δημιουργήθηκε',
+            createdDate: 'Ημερομηνία δημιουργίας',
         },
         display: {
             label: 'Εμφάνιση',
diff --git a/src/languages/es.ts b/src/languages/es.ts
index 2790fe3a..64d88baf 100644
--- a/src/languages/es.ts
+++ b/src/languages/es.ts
@@ -9436,6 +9436,8 @@ ${reportName}`,
             },
             reportField: (name, value) => `${name} es ${value}`,
             filterType: {label: 'Tipo de filtro', has: {positive: 'tiene', negative: 'no tiene'}, is: {positive: 'es', negative: 'no es'}},
+            created: 'Creado',
+            createdDate: 'Fecha de creación',
         },
         chartTitles: {
             [CONST.SEARCH.GROUP_BY.FROM]: 'De',
diff --git a/src/languages/fr.ts b/src/languages/fr.ts
index ef895335..18de89a4 100644
--- a/src/languages/fr.ts
+++ b/src/languages/fr.ts
@@ -9588,6 +9588,8 @@ Ajoutez davantage de règles de dépenses pour protéger la trésorerie de l’e
                 [CONST.SEARCH.ACTION_FILTERS.EXPORT]: 'Exporter',
             },
             filterType: {label: 'Type de filtre', has: {positive: 'a', negative: 'n’a pas'}, is: {positive: 'est', negative: 'n’est pas'}},
+            created: 'Créé',
+            createdDate: 'Date de création',
         },
         display: {
             label: 'Affichage',
diff --git a/src/languages/it.ts b/src/languages/it.ts
index 297292d6..cf183d1b 100644
--- a/src/languages/it.ts
+++ b/src/languages/it.ts
@@ -9526,6 +9526,8 @@ Aggiungi altre regole di spesa per proteggere il flusso di cassa aziendale.`,
                 [CONST.SEARCH.ACTION_FILTERS.EXPORT]: 'Esporta',
             },
             filterType: {label: 'Tipo di filtro', has: {positive: 'ha', negative: 'non ha'}, is: {positive: 'è', negative: 'non è'}},
+            created: 'Creato',
+            createdDate: 'Data di creazione',
         },
         display: {
             label: 'Visualizza',
diff --git a/src/languages/ja.ts b/src/languages/ja.ts
index b4814ff2..fcf1e79e 100644
--- a/src/languages/ja.ts
+++ b/src/languages/ja.ts
@@ -9405,6 +9405,8 @@ ${reportName}`,
                 [CONST.SEARCH.ACTION_FILTERS.EXPORT]: 'エクスポート',
             },
             filterType: {label: 'フィルタータイプ', has: {positive: '持っています', negative: '持っていません'}, is: {positive: 'は', negative: 'ではありません'}},
+            created: '作成しました',
+            createdDate: '作成日',
         },
         display: {
             label: '表示',
diff --git a/src/languages/nl.ts b/src/languages/nl.ts
index 5d748df2..c9ff74d4 100644
--- a/src/languages/nl.ts
+++ b/src/languages/nl.ts
@@ -9494,6 +9494,8 @@ er bestedingsregels toe om de kasstroom van het bedrijf te beschermen.`,
                 [CONST.SEARCH.ACTION_FILTERS.EXPORT]: 'Exporteren',
             },
             filterType: {label: 'Filtertype', has: {positive: 'heeft', negative: 'heeft niet'}, is: {positive: 'is', negative: 'is niet'}},
+            created: 'Aangemaakt',
+            createdDate: 'Aanmaakdatum',
         },
         display: {
             label: 'Weergave',
diff --git a/src/languages/pl.ts b/src/languages/pl.ts
index 907f0844..180f6545 100644
--- a/src/languages/pl.ts
+++ b/src/languages/pl.ts
@@ -9518,6 +9518,8 @@ Dodaj więcej zasad wydatków, żeby chronić płynność finansową firmy.`,
                 [CONST.SEARCH.ACTION_FILTERS.EXPORT]: 'Eksportuj',
             },
             filterType: {label: 'Typ filtra', has: {positive: 'ma', negative: 'nie ma'}, is: {positive: 'jest', negative: 'nie jest'}},
+            created: 'Utworzono',
+            createdDate: 'Data utworzenia',
         },
         display: {
             label: 'Wyświetl',
diff --git a/src/languages/pt-BR.ts b/src/languages/pt-BR.ts
index f44b1081..9a1e41c2 100644
--- a/src/languages/pt-BR.ts
+++ b/src/languages/pt-BR.ts
@@ -9494,6 +9494,8 @@ Adicione mais regras de gasto para proteger o fluxo de caixa da empresa.`,
                 [CONST.SEARCH.ACTION_FILTERS.EXPORT]: 'Exportar',
             },
             filterType: {label: 'Tipo de filtro', has: {positive: 'tem', negative: 'não tem'}, is: {positive: 'é', negative: 'não é'}},
+            created: 'Criado',
+            createdDate: 'Data de criação',
         },
         display: {
             label: 'Exibir',
diff --git a/src/languages/zh-hans.ts b/src/languages/zh-hans.ts
index c6ebe04d..6aa576eb 100644
--- a/src/languages/zh-hans.ts
+++ b/src/languages/zh-hans.ts
@@ -9157,6 +9157,8 @@ ${reportName}`,
                 [CONST.SEARCH.ACTION_FILTERS.EXPORT]: '导出',
             },
             filterType: {label: '筛选类型', has: {positive: '有', negative: '没有'}, is: {positive: '是', negative: '不是'}},
+            created: '已创建',
+            createdDate: '创建日期',
         },
         display: {
             label: '显示',

Note

You can apply these changes to your branch by copying the patch to your clipboard, then running pbpaste | git apply 😉

View workflow run

@dilshodmackbook-sketch

Copy link
Copy Markdown
Contributor Author

Quick heads-up @FitseTLT: the red test (job 4) (NavigateTests, 3 workspace split-navigator cases) is a main-side flake, not this PR. main added the Insights tab to the tab navigator, which pushed WORKSPACE_NAVIGATOR from index 4 to 5, so those tests read undefined off the old hardcoded index. This branch doesn't touch navigation and NavigateTests here is identical to main - it's actually red on a bunch of unrelated PRs right now. There's already a dedicated fix for it in #101016 (looks the navigator up by name instead of index). Once that lands I'll re-sync main and it'll go green.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants