[$250] Rename "Date" filter to "Created Date" and column header to "Created"

[sakluger]

Coming from https://expensify.slack.com/archives/C03U7DCU4/p1786133172645549

Feedback

Our date filter names are unclear and ambiguous. Users often think the data is wrong when really they just picked the wrong date filter.

Solution

On the Spend page, change Date to Created date under filter options, and change the column header to Created. This would apply to all filter Types.

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~022086840795403860978
• Upwork Job ID: 2086840795403860978
• Last Price Increase: 2026-08-20

Issue Owner

Current Issue Owner: @dilshodmackbook-sketch

[melvin-bot]

Triggered auto assignment to Design team member for new feature review - @dubielzyk-expensify (NewFeature)

[melvin-bot]

Triggered auto assignment to Contributor-plus team member for initial proposal review - @FitseTLT (External)

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~022086840795403860978

[Uzaifm127]

@FitseTLT Since there is no Melvin proposal in this issue. Can you please open it for contributors? TY!

[FitseTLT]

@MelvinBot a proposal pls

[Uzaifm127]

@FitseTLT I went through this new feature request and have the following result after back and forth:

solution-demo-web.mp4

[MelvinBot]

Proposal

Please re-state the problem that we are trying to solve in this issue.

Date filter names on the Spend (Search) page are ambiguous, leading users to think their data is wrong when they actually picked the wrong date field. We want to rename the Date filter option to Created date, and rename the results-table column header from Date to Created, across all filter Types.

What is the root cause of that problem?

This is a copy/labeling change. Both the filter option label and the table column header currently resolve to the shared translation key common.date ('Date'), which is reused in ~23 unrelated places (IOU, Travel, personal details, CSV import, etc.). So we can't just edit common.date — that would rename all of those too. We need dedicated Search keys.

• Filter option label → SearchUIUtils.ts:5547 (FILTER_VIEW_MAP[DATE].labelKey = 'common.date')
• Column header → SearchTableHeader.tsx:46, :211, :254 (translationKey: 'common.date')

What changes do you think we should make in order to solve the problem?

1. Add two dedicated Search translation keys in every src/languages/*.ts locale (e.g. under search.filters), instead of touching common.date:

// en.ts
createdDate: 'Created date', // filter option label
created: 'Created',          // column header

2. Point the Date filter label at the new key in SearchUIUtils.ts:5547:

[CONST.SEARCH.SYNTAX_FILTER_KEYS.DATE]: {
    labelKey: 'search.filters.createdDate', // was 'common.date'
    icon: 'CalendarSolid',
},

3. Point the DATE column header at the new key in all three header builders — getExpenseHeaders (:46), taskHeaders (:211), and getExpenseReportHeaders (:254) — so it applies to all Types:

translationKey: 'search.created', // was 'common.date'

One decision point for the reviewer: sort dropdown & columns-settings

The same DATE column label is also produced by getSearchColumnTranslationKey (SearchUIUtils.ts:4532), which feeds the sort-by dropdown, the columns-settings (show/hide columns) list, the Save search page, and export column labels. The issue only asks to rename the visible column header and the filter option, so the minimal change leaves those as "Date". But if we want consistency (the header says "Created" while the columns-settings toggle still says "Date"), we should also switch TABLE_COLUMNS.DATE in getSearchColumnTranslationKey to return search.created. Recommend confirming which behavior Design wants.

What alternative solutions did you explore?

Editing common.date directly — rejected, it would rename ~23 unrelated date fields app-wide. Adding a per-Type override was also considered but is unnecessary since the three header builders already cover all Types.

---

Next Steps for Contributor+ team:
To accept: @MelvinBot implement this proposal to create a draft PR.
To refine: @MelvinBot <your feedback>
To reject: Explain why you are rejecting Melvin's proposal.

[Uzaifm127]

@FitseTLT Gentle bump here for updates. Thanks

[FitseTLT]

🆘 C+ Help wanted