Add move option to search selected menu #62270

jnowakow · 2025-05-19T09:41:53Z

Explanation of Change

Fixed Issues

$ #61770
PROPOSAL: N/A

Tests

Go to reports
Select some transactions that are eligible to be moved
Verify that move option is available
Verify that expenses are moved correctly.

Verify that no errors appear in the JS console

Offline tests

Go to reports
Select some transactions that are eligible to be moved
Verify that move option is available
Verify that expenses are moved correctly.

QA Steps

// TODO: These must be filled out, or the issue title must include "[No QA]."

Go to reports
Select some transactions that are eligible to be moved
Verify that move option is available
Verify that expenses are moved correctly.

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
- MacOS: Desktop
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 verified there are no new alerts related to the canBeMissing param for useOnyx
I followed proper code patterns (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 shown in the product is localized by adding it to src/languages/* files and using the translation method
  - If any non-english text was added/modified, I used JaimeGPT to get English > Spanish translation. I then posted it in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:
- I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
- 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)
- I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
- I verified the JSDocs style guidelines (in STYLE.md) were followed
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)
I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
I verified any variables that can be defined as constants (ie. in CONST.ts or at the top of the file that uses the constant) are defined as such
I verified that if a function's arguments changed that all usages have also been updated correctly
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.
If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
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

iosWeb.mov

MacOS: Chrome / Safari

web.mov

MacOS: Desktop

melvin-bot · 2025-05-19T09:41:58Z

@DylanDylann 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]

jnowakow · 2025-05-19T09:42:08Z

cc @luacmartins

src/components/Search/index.tsx

src/CONST.ts

src/components/Search/types.ts

src/libs/Navigation/linkingConfig/RELATIONS/SEARCH_TO_RHP.ts

DylanDylann · 2025-05-19T16:57:23Z

Move expenses doesn't work after refresh page

Screen.Recording.2025-05-19.at.23.55.06.mov

…k-move-transactions-on-search

jnowakow · 2025-05-20T07:54:06Z

Move expenses doesn't work after refresh page

Screen.Recording.2025-05-19.at.23.55.06.mov

This bug is already present on search page for example on hold RHP. Selected transactions are stored in context so after refresh it's cleared. I think this should be handled as separate issue

search.mov

luacmartins · 2025-05-20T19:15:56Z

I agree that's an existing bug. Maybe we can just dismiss the modal after the refresh, but that should be handled in a follow up

src/pages/Search/SearchMoveTransactions.tsx

…k-move-transactions-on-search

src/pages/Search/SearchPage.tsx

DylanDylann · 2025-05-21T09:49:27Z

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
- MacOS: Desktop
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 there are no new alerts related to the canBeMissing param for useOnyx
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 shown in the product is localized by adding it to src/languages/* files and using the translation method
- I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
- 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)
- I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
- I verified the JSDocs style guidelines (in STYLE.md) were followed
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)
I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
I verified any variables that can be defined as constants (ie. in CONST.ts or at the top of the file that uses the constant) are defined as such
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.
If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
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

Screen.Recording.2025-05-21.at.16.41.21.mov

Android: mWeb Chrome

Screen.Recording.2025-05-21.at.16.35.25.mov

iOS: HybridApp

Screen.Recording.2025-05-21.at.16.44.33.mov

iOS: mWeb Safari

Screen.Recording.2025-05-21.at.16.31.27.mov

MacOS: Chrome / Safari

Screen.Recording.2025-05-21.at.16.02.18.mov

MacOS: Desktop

Screen.Recording.2025-05-21.at.16.48.25.mov

luacmartins

Thanks for addressing the comments

OSBotify · 2025-05-21T16:01:26Z

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

github-actions · 2025-05-21T18:30:58Z

🚀 Deployed to staging by https://github.com/luacmartins in version: 9.1.48-0 🚀

platform	result
🖥 desktop 🖥	failure ❌
🕸 web 🕸	success ✅
🤖 android 🤖	success ✅
🍎 iOS 🍎	failure ❌

dangrous · 2025-05-21T20:25:00Z

src/pages/Search/SearchTransactionsChangeReport.tsx

+        return [...reports];
+    }, [allReports, selectedTransactions]);
+
+    const selectReport = (item: ReportListItem) => {


Hi! This is causing #62500 - we need to add similar logic to this so that it doesn't try to move the report if it's being moved to the report it's already on.

github-actions · 2025-05-21T21:01:38Z

🚀 Deployed to staging by https://github.com/luacmartins in version: 9.1.48-0 🚀

platform	result
🖥 desktop 🖥	success ✅
🕸 web 🕸	success ✅
🤖 android 🤖	success ✅
🍎 iOS 🍎	failure ❌

github-actions · 2025-05-22T10:53:38Z

🚀 Deployed to staging by https://github.com/luacmartins in version: 9.1.49-5 🚀

platform	result
🖥 desktop 🖥	success ✅
🕸 web 🕸	success ✅
🤖 android 🤖	success ✅
🍎 iOS 🍎	success ✅

github-actions · 2025-05-23T19:05:49Z

🚀 Deployed to production by https://github.com/arosiclair in version: 9.1.50-0 🚀

platform	result
🖥 desktop 🖥	success ✅
🕸 web 🕸	success ✅
🤖 android 🤖	failure ❌
🍎 iOS 🍎	success ✅

Add move option to search selected menu

bc2fed4

jnowakow requested a review from a team as a code owner May 19, 2025 09:41

melvin-bot bot requested review from DylanDylann and removed request for a team May 19, 2025 09:41

jnowakow mentioned this pull request May 19, 2025

[Due for payment 2025-05-30] [Due for payment 2025-05-27] [Report Creation UI] Add Move expense to the bulk action menu #61770

Open

2 tasks

Fix typescript

1855a37

luacmartins self-requested a review May 19, 2025 15:56

luacmartins assigned jnowakow May 19, 2025

luacmartins requested changes May 19, 2025

View reviewed changes

jnowakow added 2 commits May 20, 2025 09:43

Apply review suggestions

3e2724d

Merge branch 'main' of github.com:Expensify/App into jnowakow/add-bul…

7ff3d65

…k-move-transactions-on-search

jnowakow requested a review from luacmartins May 20, 2025 10:46

luacmartins requested changes May 20, 2025

View reviewed changes

src/pages/Search/SearchMoveTransactions.tsx Outdated Show resolved Hide resolved

src/pages/Search/SearchMoveTransactions.tsx Outdated Show resolved Hide resolved

jnowakow added 2 commits May 21, 2025 09:26

Merge branch 'main' of github.com:Expensify/App into jnowakow/add-bul…

1e8a870

…k-move-transactions-on-search

Rename screen

24b2799

jnowakow requested a review from luacmartins May 21, 2025 08:14

DylanDylann reviewed May 21, 2025

View reviewed changes

src/pages/Search/SearchPage.tsx Outdated Show resolved Hide resolved

Review suggestion

5c37f43

DylanDylann approved these changes May 21, 2025

View reviewed changes

luacmartins approved these changes May 21, 2025

View reviewed changes

luacmartins merged commit e9cdd22 into Expensify:main May 21, 2025
17 checks passed

This was referenced May 21, 2025

Investigate workflow job failing on main: e2ePerformanceTests / Build apk from delta ref / Build Android app #62490

Closed

Investigate workflow job failing on main: e2ePerformanceTests / Build apk from baseline / Build Android app #62491

Closed

github-actions bot mentioned this pull request May 21, 2025

Deploy Checklist: New Expensify 2025-05-21 #62497

Closed

dangrous reviewed May 21, 2025

View reviewed changes

dangrous mentioned this pull request May 21, 2025

[CP Staging] Fix moving expenses from Search #62515

Merged

51 tasks

nkdengineer mentioned this pull request May 22, 2025

[$250] Move expense - Expense can be moved to report of deleted workspace #62552

Open

8 tasks

grgia mentioned this pull request May 22, 2025

[Due for payment 2025-05-30] [Report Creation UI] [$250] Expense - Not here page opens when admin clicks Move expense in member's report #62575

Open

8 tasks

Add move option to search selected menu #62270

Add move option to search selected menu #62270

Uh oh!

Conversation

jnowakow commented May 19, 2025

Explanation of Change

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

Uh oh!

melvin-bot bot commented May 19, 2025

Uh oh!

jnowakow commented May 19, 2025

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

DylanDylann commented May 19, 2025

Uh oh!

jnowakow commented May 20, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

luacmartins commented May 20, 2025

Uh oh!

Uh oh!

Uh oh!

Uh oh!

DylanDylann commented May 21, 2025

Reviewer Checklist

Screenshots/Videos

Uh oh!

luacmartins left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

OSBotify commented May 21, 2025

Uh oh!

github-actions bot commented May 21, 2025

Uh oh!

dangrous May 21, 2025

Choose a reason for hiding this comment

Uh oh!

github-actions bot commented May 21, 2025

Uh oh!

github-actions bot commented May 22, 2025

Uh oh!

github-actions bot commented May 23, 2025

Uh oh!

Uh oh!

jnowakow commented May 20, 2025 •

edited

Loading