Skip to content

Show Submit/Approve/Pay options when all expenses within a report are selected#84077

Merged
puneetlath merged 26 commits intoExpensify:mainfrom
Krishna2323:krishna2323/issue/72502-2
Mar 13, 2026
Merged

Show Submit/Approve/Pay options when all expenses within a report are selected#84077
puneetlath merged 26 commits intoExpensify:mainfrom
Krishna2323:krishna2323/issue/72502-2

Conversation

@Krishna2323
Copy link
Contributor

@Krishna2323 Krishna2323 commented Mar 3, 2026

Explanation of Change

Fixed Issues

$ #72502
PROPOSAL:

Tests

  • Same as QA Steps

  • Verify that no errors appear in the JS console

Offline tests

  • Same as QA Steps

QA Steps

Submit action via selection mode

  1. Open an expense report where the primary action is "Submit"
  2. Select all expenses using the checkboxes
  3. Verify the "X selected" dropdown appears
  4. Open the dropdown — verify "Submit" appears at the top
  5. Click "Submit"
  6. Verify the report is submitted, selections are cleared, and no submit animation plays

Approve action via selection mode

  1. Open a submitted expense report as an approver
  2. Select all expenses
  3. Open the "X selected" dropdown — verify "Approve" appears at the top
  4. Click "Approve"
  5. Verify the report is approved, selections are cleared, and no approve animation plays

Pay action via selection mode

  1. Open an approved expense report ready to be paid
  2. Select all expenses
  3. Open the "X selected" dropdown — verify "Pay $X.XX" appears at the top with a right arrow
  4. Click "Pay $X.XX" — verify a submenu opens with payment methods
  5. Select "Pay elsewhere"
  6. Verify payment processes, selections are cleared, no paid animation plays, and "You're all set!" RHP does not open
  7. Verify Pay is no longer shown in the dropdown

Approve with delegate restriction (bug fix verification)

  1. Log in as a delegate with restricted access
  2. Open a submitted expense report
  3. Select all expenses
  4. Open the "X selected" dropdown and click "Approve"
  5. Verify the "no access" modal appears
  6. Dismiss the modal
  7. Verify selections are still active (not cleared)

Approve with held expenses

  1. Open a submitted expense report where some expenses are on hold
  2. Select all expenses
  3. Open the "X selected" dropdown and click "Approve"
  4. Verify the hold menu appears
  5. Verify selections are cleared

Pay as business

  1. Open an approved expense report, select all expenses
  2. Open Pay submenu, select "Pay as business" (if available)
  3. Verify payment processes without the "You're all set!" RHP opening
  4. Verify selections are cleared

Pay with delegate restriction

  1. Log in as a delegate with restricted access
  2. Open an approved expense report, select all expenses
  3. Open Pay submenu, select a payment method
  4. Verify the "no access" modal appears
  5. Verify selections are not cleared

Partial selection (no report-level actions)

  1. Open an expense report with 3+ expenses
  2. Select only some (not all) expenses
  3. Open the "X selected" dropdown
  4. Verify Submit/Approve/Pay do not appear — only transaction-level actions

###Non-regression: regular Submit button

  1. Open a draft expense report, do not select any expenses
  2. Click "Submit" in the header
  3. Verify the submit animation plays and report is submitted

Non-regression: regular Approve button

  1. Open a submitted report as approver, do not select any expenses
  2. Click "Approve" in the header
  3. Verify approval completes normally

Non-regression: regular Pay button

  1. Open an approved report, do not select any expenses
  2. Click "Pay" in the header, select "Pay elsewhere"
  3. Verify the paid animation plays and payment completes

Non-regression: "More" dropdown

  1. Open any expense report, do not select any expenses
  2. Click the "More" dropdown
  3. Verify all secondary actions still work normally

Offline behavior

  1. Go offline
  2. Open an expense report, select all expenses
  3. Verify Submit/Approve appear and can be clicked
  4. Verify Pay options are disabled (KYCWall isDisabled={isOffline})
  • 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 new assets were added or existing ones were modified, I verified that:
    • The assets are optimized and compressed (for SVG files, run npm run compress-svg)
    • The assets load correctly across all supported platforms.
  • 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_native.mp4
Android: mWeb Chrome
android_chrome.mp4
iOS: Native
ios_native.mp4
iOS: mWeb Safari
ios_safari.mp4
MacOS: Chrome / Safari

Submit/Approve/Pay action via selection mode

test_1.2.4.mp4

Approve with delegate restriction (bug fix verification)

test_3.mp4

Approve with held expenses

test_5.mp4

Pay as business

test_6.mp4

Partial selection (no report-level actions)

test_8.mp4

Non-regression: regular Submit/Approve/Pay button

test_9.10.11.mp4

Offline behavior

test_9.10.12.mp4

Pay with delegate restriction

delegate_pay_test.mp4

… selected

Signed-off-by: krishna2323 <belivethatkg@gmail.com>
…firmApproval.

Signed-off-by: krishna2323 <belivethatkg@gmail.com>
Signed-off-by: krishna2323 <belivethatkg@gmail.com>
Signed-off-by: krishna2323 <belivethatkg@gmail.com>
@codecov
Copy link

codecov bot commented Mar 3, 2026

Codecov Report

❌ Looks like you've decreased code coverage for some files. Please write tests to increase, or at least maintain, the existing level of code coverage. See our documentation here for how to interpret this table.

Files with missing lines Coverage Δ
src/hooks/usePaymentOptions.ts 0.00% <0.00%> (ø)
src/libs/PaymentUtils.ts 77.77% <66.66%> (-0.53%) ⬇️
src/components/MoneyReportHeaderKYCDropdown.tsx 0.00% <0.00%> (ø)
src/components/MoneyReportHeader.tsx 0.00% <0.00%> (ø)
... and 11 files with indirect coverage changes

Signed-off-by: krishna2323 <belivethatkg@gmail.com>
Made-with: Cursor
Signed-off-by: krishna2323 <belivethatkg@gmail.com>
@Krishna2323 Krishna2323 marked this pull request as ready for review March 5, 2026 02:40
@Krishna2323 Krishna2323 requested review from a team as code owners March 5, 2026 02:40
@melvin-bot melvin-bot bot requested a review from situchan March 5, 2026 02:40
@melvin-bot
Copy link

melvin-bot bot commented Mar 5, 2026

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

@melvin-bot melvin-bot bot requested review from heyjennahay and removed request for a team March 5, 2026 02:40
@Krishna2323
Copy link
Contributor Author

Not sure why ESLint check is failing.

Signed-off-by: krishna2323 <belivethatkg@gmail.com>
Copy link

@chatgpt-codex-connector chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: b05d4ed6bd

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

Signed-off-by: krishna2323 <belivethatkg@gmail.com>
Signed-off-by: krishna2323 <belivethatkg@gmail.com>
Signed-off-by: krishna2323 <belivethatkg@gmail.com>
@Krishna2323
Copy link
Contributor Author

@codex review

Copy link

@chatgpt-codex-connector chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 0472c54bbe

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

@JmillsExpensify
Copy link
Contributor

Review on-going. Waiting for updates.

@situchan
Copy link
Contributor

@Krishna2323 conflicts. and please check #84077 (review)

…02-2

Made-with: Cursor

# Conflicts:
#	src/components/MoneyReportHeader.tsx
#	src/components/MoneyReportHeaderKYCDropdown.tsx
Signed-off-by: krishna2323 <belivethatkg@gmail.com>
@Krishna2323
Copy link
Contributor Author

@situchan all done!

@melvin-bot melvin-bot bot requested a review from puneetlath March 10, 2026 20:55
@JmillsExpensify
Copy link
Contributor

Nice! @puneetlath another one of your improvements ready for review.

puneetlath
puneetlath previously approved these changes Mar 12, 2026
@puneetlath
Copy link
Contributor

Sorry for the delay @Krishna2323. Mind fixing the conflicts and then pinging me?

heyjennahay
heyjennahay previously approved these changes Mar 12, 2026
Copy link
Contributor

@heyjennahay heyjennahay left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Product change 👍

@Krishna2323 Krishna2323 dismissed stale reviews from heyjennahay and puneetlath via e9e75f2 March 13, 2026 01:47
@Krishna2323
Copy link
Contributor Author

@puneetlath conflicts resolved.

@puneetlath puneetlath merged commit 6c41212 into Expensify:main Mar 13, 2026
34 checks passed
@github-actions
Copy link
Contributor

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

@OSBotify
Copy link
Contributor

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

@OSBotify
Copy link
Contributor

🚀 Deployed to staging by https://github.com/puneetlath in version: 9.3.38-0 🚀

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

@IuliiaHerets
Copy link

Hi @Krishna2323. Do we have QA steps here?

@Krishna2323
Copy link
Contributor Author

@IuliiaHerets yes, it's in the OP's QA Test section.

@situchan
Copy link
Contributor

@IuliiaHerets and this feature is web-only. Not available yet on mobile

@jponikarchuk
Copy link

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

@jponikarchuk
Copy link

This PR failing because of the issue #85413
This issue is reproducible in: Web

@puneetlath
Copy link
Contributor

Closed that issue as not a bug.

@OSBotify
Copy link
Contributor

🚀 Deployed to production by https://github.com/cristipaval in version: 9.3.38-4 🚀

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

9 participants