Feat: Add 'Move to report' in the 'More' menu of a one-expense report by nyomanjyotisa · Pull Request #84512 · Expensify/App

nyomanjyotisa · 2026-03-08T15:09:54Z

Explanation of Change

Add "Move to report" in the secondary actions when there's exactly one transaction that can be moved

Fixed Issues

$ #83884
PROPOSAL: #83884 (comment)

Tests

Same as QA Steps

Verify that no errors appear in the JS console

Offline tests

Same as QA Steps

QA Steps

Create an expense in a workspace
Open the expense
Click on "More"
Verify that the "Move to report" option is displayed
Click on the "Move to report" option
Move the expense to another report
Verify that the operation was successful

Verify that no errors appear in the JS console

PR Author Checklist

Screenshots/Videos

Android: Native

Android-Native.mp4

Android: mWeb Chrome

Android-mWeb.Chrome.mp4

iOS: Native

iOS-Native.mp4

iOS: mWeb Safari

iOS-mWeb.Safari.mp4

MacOS: Chrome / Safari

MacOS-Chrome.mp4

codecov · 2026-03-08T15:17:02Z

Codecov Report

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

Files with missing lines	Coverage Δ
src/CONST/index.ts	`93.54% <ø> (ø)`
src/libs/ReportSecondaryActionUtils.ts	`92.65% <100.00%> (+0.22%)`	⬆️
src/components/MoneyRequestHeader.tsx	`0.00% <0.00%> (ø)`
src/components/MoneyReportHeader.tsx	`0.00% <0.00%> (ø)`
... and 15 files with indirect coverage changes

melvin-bot · 2026-03-09T13:56:22Z

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

ZhenjaHorbach · 2026-03-09T13:57:58Z

src/libs/ReportSecondaryActionUtils.ts

        options.push(CONST.REPORT.TRANSACTION_SECONDARY_ACTIONS.DUPLICATE);
    }

+    if (


Let's add tests for this case

Got it, added the test case

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 8b06c1a6e2

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

chatgpt-codex-connector · 2026-03-09T14:09:06Z

src/components/MoneyReportHeader.tsx

+        if (transactions.length !== 1) {
+            return false;


Base single-expense visibility on non-deleted transactions

canMoveSingleExpense checks transactions.length, but this header builds secondaryActions from nonPendingDeleteTransactions (the visible list). When a report has one visible expense plus another expense pending deletion, getSecondaryReportActions can include MOVE_EXPENSE while this guard returns false, so the new menu item is incorrectly hidden until the pending delete finishes. This regresses the intended “one-expense report” behavior for in-flight delete states.

Useful? React with 👍 / 👎.

~~@ZhenjaHorbach When there is a pending delete expense, do you think we should include the MOVE_EXPENSE option? If so, we can check it with nonPendingDeleteTransactions instead of transactions~~ I guess we should, to match the other single expense secondary action button like Split, Merge and Duplicate expense. Updated!

trjExpensify

Agreed product change. 👍

ZhenjaHorbach · 2026-03-10T11:52:41Z

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

2026-03-10.12.45.13.mov

Android: mWeb Chrome

2026-03-10.12.42.52.mov

iOS: HybridApp

2026-03-10.12.45.13.mov

iOS: mWeb Safari

2026-03-10.12.42.52.mov

MacOS: Chrome / Safari

2026-03-10.12.37.51.mov

aldo-expensify · 2026-03-10T18:45:56Z

@nyomanjyotisa please resolve conflicts 🙇

nyomanjyotisa · 2026-03-11T05:59:39Z

@aldo-expensify conflict resolved 👍

github-actions · 2026-03-11T17:40:46Z

🚧 @aldo-expensify has triggered a test Expensify/App build. You can view the workflow run here.

github-actions · 2026-03-11T17:47:43Z

🧪🧪 Use the links below to test this adhoc build on Android, iOS, and Web. Happy testing! 🧪🧪
Built from App PR #84512.

Android 🤖	iOS 🍎
❌ FAILED ❌	❌ FAILED ❌
The QR code can't be generated, because the Android build failed	The QR code can't be generated, because the iOS build failed

Web 🕸️
❌ FAILED ❌
The QR code can't be generated, because the Web build failed

👀 View the workflow run that generated this build 👀

OSBotify · 2026-03-11T20:05:47Z

🚀 Deployed to staging by https://github.com/aldo-expensify in version: 9.3.36-0 🚀

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

mitarachim · 2026-03-11T21:39:43Z

Deploy Blocker #84976 was identified to be related to this PR.

mitarachim · 2026-03-12T01:38:19Z

Deploy Blocker #85012 was identified to be related to this PR.

mitarachim · 2026-03-12T02:17:35Z

Deploy Blocker #85014 was identified to be related to this PR.

OSBotify · 2026-03-12T22:50:29Z

🚀 Deployed to production by https://github.com/luacmartins in version: 9.3.36-10 🚀

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

Feat: Add 'Move to report' in the 'More' menu of a one-expense report

f474cec

melvin-bot bot assigned nyomanjyotisa Mar 8, 2026

nyomanjyotisa added 4 commits March 8, 2026 23:22

prettier fix

02b9eef

lint fix

9cbeee8

lint fix

b928dbb

Add 'Move to report' in MoneyRequestHeader

8b06c1a

nyomanjyotisa marked this pull request as ready for review March 9, 2026 13:56

nyomanjyotisa requested review from a team as code owners March 9, 2026 13:56

melvin-bot bot requested review from ZhenjaHorbach and removed request for a team March 9, 2026 13:56

melvin-bot bot requested review from trjExpensify and removed request for a team March 9, 2026 13:56

ZhenjaHorbach reviewed Mar 9, 2026

View reviewed changes

chatgpt-codex-connector bot reviewed Mar 9, 2026

View reviewed changes

nyomanjyotisa added 3 commits March 9, 2026 22:24

test: add unit tests for ReportSecondaryActionUtils

a154f61

minor fix

c1e6c4a

Merge branch 'main' into issue-83884

2e09695

trjExpensify previously approved these changes Mar 10, 2026

View reviewed changes

ZhenjaHorbach approved these changes Mar 10, 2026

View reviewed changes

melvin-bot bot requested a review from aldo-expensify March 10, 2026 11:53

Merge branch 'main' into issue-83884

3eb5d68

nyomanjyotisa dismissed trjExpensify’s stale review via 3eb5d68 March 11, 2026 05:58

aldo-expensify approved these changes Mar 11, 2026

View reviewed changes

aldo-expensify merged commit c1334fe into Expensify:main Mar 11, 2026
31 checks passed

OSBotify mentioned this pull request Mar 11, 2026

Deploy Checklist: New Expensify 2026-03-11 #84953

Closed

vincdargento mentioned this pull request Mar 11, 2026

Expense - Nothing happens after clicking Create report when there is no workspace #84974

Closed

7 tasks

mitarachim mentioned this pull request Mar 11, 2026

Expense - Remove from report option is shown when the expense is unreported #84976

Closed

7 tasks

aldo-expensify mentioned this pull request Mar 11, 2026

[CP Staging] Revert "Feat: Add 'Move to report' in the 'More' menu of a one-expense report" #84984

Merged

50 tasks

mitarachim mentioned this pull request Mar 12, 2026

Expense - Create report button shows one workspace, but report is created in another workspace #85012

Closed

7 tasks

mitarachim mentioned this pull request Mar 12, 2026

Expense- Report field is disabled when per diem rates are removed, but Move to report is shown #85014

Closed

7 tasks

MelvinBot mentioned this pull request Mar 12, 2026

[Due for payment 2026-03-19] Report - Cancel payment doesn't work and leads to blank page #85019

Closed

7 tasks

melvin-bot bot mentioned this pull request Mar 12, 2026

[Due for payment 2026-03-19] [$250] Improvement: “Move expense” to “Move to report” and show both actions in one-expense report menu #83884

Open

7 tasks

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Feat: Add 'Move to report' in the 'More' menu of a one-expense report#84512

Feat: Add 'Move to report' in the 'More' menu of a one-expense report#84512
aldo-expensify merged 9 commits intoExpensify:mainfrom
nyomanjyotisa:issue-83884

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

6 participants

Conversation

Uh oh!

Explanation of Change

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

Uh oh!

Uh oh!

Codecov Report

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Reviewer Checklist

Screenshots/Videos

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

6 participants