Feature: Implement ChangeTransactionsReport

[waterim]

Details

Fixed Issues

$ #57468
PROPOSAL: N/A

Tests

1. In OldDot, create two reports
2. Add a transaction to one of them
3. In NewDot, navigate to the report with the transaction
4. Select the report row
5. Change it to the other report
6. Verify that the transaction changes reports
7. Verify that the money request preview is updated
8. Verify that the report previews are updated
9. Verify that the MOVEDTRANSACTION reportAction is added to the transaction thread

• Verify that no errors appear in the JS console

Offline tests

Same as tests

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 / Chrome
  • iOS / native
  • iOS / 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 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 the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
  • 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 verified the translation was requested/reviewed 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 approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
  • 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.js 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 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
  • If we are not using the full Onyx data that we loaded, I've added the proper selector in order to ensure the component only re-renders when the data it is using changes
  • 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(themeColors.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 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.
• 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 author checklist, including those that don't apply to this PR.

[waterim]

@luacmartins can you please provide more detailed steps for testing this?
Ive updated the code, but Im not sure what Ive missed and want to test it nicely
Also its ready for the initial review

[luacmartins]

@waterim you can try the following:

1. In OldDot, create two reports
2. Add a transaction to one of them
3. In NewDot, navigate to the report with the transaction
4. Select the report row
5. Change it to the other report
6. Verify that the transaction changes reports
7. Verify that the money request preview is updated
8. Verify that the report previews are updated
9. Verify that the MOVEDTRANSACTION reportAction is added to the transaction thread

Screen.Recording.2025-03-27.at.4.06.49.PM.mov

I tried the steps above, but it doesn't seem like we trigger an API request at all. Also the report name shown in the menu item seems incorrect, note that's showing Chat report when the transaction in the video is on report with name Expense Report #4280177799669043

[luacmartins]

@waterim do you have an ETA in mind to get this one in review?

[waterim]

Yes, im working now on this one

[waterim]

Will open a PR today evening

[OSBotify]

✋ 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]

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

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

[mvtglobally]

@luacmartins @DylanDylann @sumo-slonik What do we need to QA here?

[luacmartins]

@mvtglobally I added steps to the OP

[github-actions]

🚀 Deployed to production by https://github.com/marcaaron in version: 9.1.28-15 🚀

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

[rayane-d]

Coming from #60225 (BugZero Checklist), a case was missed during the original design: we need to remove the existing logic that adds an optimistic moved tracked expense MODIFIED_EXPENSE report action to avoid causing a duplicate action with MOVED_TRANSACTION report action when moving the tracked expense from self DM to the workspace report using the whisper message buttons.

[allgandalf]

We should have got the reportName from getReportName(report), more details in this issue:

• [$250] [Due for payment 2025-05-08] Track expense - "moved this expense to" message shows "unavailable workspace" in offline mode #60979

[ishpaul777]

Coming from #60251 {BZ checklist}, We weren't correctly updating the IOU action when moving reports so it left a "ghost" message behind. its fixed in #61221

[hoangzinh]

We forgot to handle this action type in LHN, which causes this bug #61009 (comment)

[ahmedGaber93]

Coming from #69109, it is an edge case when moving hold report to selfDM, the "On Hold" status is not removed, and we handled it here #70593