[$75] Update `Save search` to `Save view`

[JmillsExpensify]

In a recent research call, a customer was confused that we were calling this page Saved search give that what you are saving is a view, which takes either table or graphical form.

I think that's super fair, and also something that puts us in line with the rest of the industry. As a result, let's

• Update the page title to Save view
• Update the button to Save view
• No need to change the route/URL

This will be a $75 issue given the small scope.

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~022056659995479245550
• Upwork Job ID: 2056659995479245550
• Last Price Increase: 2026-05-19

Issue Owner

Current Issue Owner: @mdneyazahmad

[melvin-bot]

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

[melvin-bot]

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

[melvin-bot]

Upwork job price has been updated to $75

[yusufdeveloper2903]

🚨 Edited by proposal-police: This proposal was edited at 2026-05-19 08:58:11 UTC.

Proposal

What is the root cause of that problem?

This is a copy issue, not a logic bug. The page title and the submit button on the Save search RHP are both rendered from the same translation key, search.saveSearch, in src/pages/Search/SearchSavePage.tsx#L169-L172:

<HeaderWithBackButton title={translate('search.saveSearch')} />
…
submitButtonText={translate('search.saveSearch')}

search.saveSearch is defined in src/languages/en.ts#L7843 as 'Save search' and in src/languages/es.ts#L7631 as 'Guardar búsqueda'. Because the title and the CTA share one key, the customer-reported wording can be corrected with a single value edit per locale — no other call sites consume this key.

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

A copy-only change to the two locale files. The scope is exactly the two strings the issue lists (page title + button); related keys (savedSearchesTitle, deleteSavedSearch, deleteSavedSearchConfirm, saveSearchTooltip) describe the saved-searches list page / tooltip and are explicitly out of scope here — the issue says only the title and button on this RHP need updating, and the route stays the same.

1. src/languages/en.ts (L7843)

-        saveSearch: 'Save search',
+        saveSearch: 'Save view',

2. src/languages/es.ts (L7631)

-        saveSearch: 'Guardar búsqueda',
+        saveSearch: 'Guardar vista',

That's it. Because both HeaderWithBackButton title and FormProvider submitButtonText already read translate('search.saveSearch') (SearchSavePage.tsx L169 + L172), both UI strings flip together with this single key change. No component, route, Onyx, or type changes are required, and TranslationPaths is unaffected since the key name is preserved.

What alternative solutions did you explore?

• Rename the key (saveSearch → saveView). Rejected: pure churn for a value-only copy change; risks compile breakage if a consumer is missed and offers zero user-facing benefit since both render sites already share the same key.
• Also rewrite savedSearchesTitle / deleteSavedSearch* / saveSearchTooltip to use "view". Rejected: the issue explicitly limits the fix to the Save-search RHP's page title + button. Those other strings belong to the saved-searches list page and a contextual tooltip; touching them expands scope beyond what the issue (and the customer feedback that produced it) asks for and should be a separate copy pass if Product wants the wider rename later.
• Hardcode the new copy in SearchSavePage.tsx. Rejected: bypasses i18n, leaves es.ts stale, and would surface MISSING TRANSLATION for Spanish users.

[github-actions]

⚠️ @yusufdeveloper2903 Your proposal is a duplicate of an already existing proposal and has been automatically withdrawn to prevent spam. Please review the existing proposals before submitting a new one.