Skip to content

Rename Search "Date" filter to "Created date" and column to "Created" for report-style types - #99216

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

Rename Search "Date" filter to "Created date" and column to "Created" for report-style types#99216
dilshodmackbook-sketch wants to merge 9 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 report-style types only — expense-report and invoice (invoice is treated like a report). Every other type (expense, trip, chat, task), the opened single-report table, and every non-Search surface keep Date.

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 (w62 → w80, min-width 48 → 72) only for those report-style types so the longer Created header doesn't clip against its active-sort caret. The date: query key and sortBy wire value never change, so saved searches, deep links and optimistic rows keep working — only visible labels move, and only in report-style Search.

Fixed Issues

$ #98148
PROPOSAL: #98148 (comment)

Tests

  1. Open Search and switch type to Expenses — verify the date filter option and the column header both read Date.
  2. Switch type to Expense reports and Invoices — verify the filter option reads Created date and the column header, Sort by, Edit columns and Export current view (CSV) all read Created.
  3. Switch type to Trips, Chats and Tasks — verify they all keep Date.
  4. Open a single report — verify its table and its Columns menu still read Date.
  5. Verify an unrelated Date label (e.g. the IOU 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
Android: mWeb Chrome
iOS: Native
iOS: mWeb Safari
MacOS: Chrome / Safari
demo-video.mp4
Image

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

dilshodmackbook-sketch and others added 7 commits August 18, 2026 20:26
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.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…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).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…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.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@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
@codecov

codecov Bot commented Aug 21, 2026

Copy link
Copy Markdown

Codecov Report

✅ Changes either increased or maintained existing code coverage, great job!

Files with missing lines Coverage Δ
src/components/Search/ExpenseFlatSearchView.tsx 100.00% <ø> (ø)
...em/TransactionListItem/TransactionListItemWide.tsx 0.00% <ø> (ø)
.../SearchList/ListItem/TransactionListItem/index.tsx 0.00% <ø> (ø)
src/components/Search/SearchList/ListItem/types.ts 100.00% <ø> (ø)
src/components/Search/SearchStaticList.tsx 40.81% <ø> (ø)
src/components/Search/SortableTableHeader.tsx 43.47% <ø> (ø)
...ents/TransactionItemRow/TransactionItemRowWide.tsx 98.38% <100.00%> (+0.01%) ⬆️
src/components/TransactionItemRow/index.tsx 83.87% <ø> (ø)
src/hooks/useSearchBulkActions.ts 70.83% <100.00%> (ø)
...rsContentPage/SearchAdvancedFiltersContentBase.tsx 0.00% <ø> (ø)
... and 11 more
... and 12 files with indirect coverage changes

Comment thread src/components/ColumnsSettingsList.tsx Outdated
Comment thread src/components/Search/SearchTableHeader.tsx
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

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review: Didn't find any major issues. Another round soon, please!

Reviewed commit: 782ec4d3e8

ℹ️ 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

Thanks for the heads-up. All 10 non-English locales already include the two new keys (created / createdDate) with proper translations in this PR, so nothing needs auto-generating. Happy for someone with write access to run the workflow to double-check if preferred.

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.

1 participant