Skip to content

[HOLD] Allow admins to merge card + cash expenses across draft reports - #101028

Closed
youssef-lr wants to merge 3 commits into
mainfrom
youssef-lr-app-678389-manual-merge-expenses-drafts
Closed

youssef-lr wants to merge 3 commits into
mainfrom
youssef-lr-app-678389-manual-merge-expenses-drafts

Conversation

@youssef-lr

@youssef-lr youssef-lr commented Sep 12, 2026 •

Copy link
Copy Markdown
Contributor

Explanation of Change

Removes the admin same-report-only shortcut in getTransactionsForMerging. Admins can now discover merge candidates across different draft reports and workspaces, not just the report they triggered merge from. Non-admin managers reviewing a processing report keep the same-report restriction unchanged.

The offline filter now checks admin access per-candidate against that candidate's own workspace policy. If the policy is not in the local cache the candidate is excluded rather than assumed accessible.

MergeTransactionsListContent subscribes to allPolicies and allReports and forwards them for the offline per-candidate check.

Fixed Issues

$ https://github.com/Expensify/Expensify/issues/678389
PROPOSAL:

Tests

  • Verify that no errors appear in the JS console

Offline tests

  • As an admin, go offline, open a card expense on one draft report, tap Merge — verify cash expenses from other draft reports (same submitter, same or different workspace where you are admin) appear as candidates.
  • Repeat with no cached policy for one workspace — verify its expenses do not appear as candidates.
  • As a non-admin manager reviewing a processing report, go offline, tap Merge — verify only same-report expenses appear.

QA Steps

  • As a workspace admin, open a card expense on a draft report, tap Merge — verify cash expenses from other draft reports of the same submitter (same workspace) appear.

  • As a workspace admin, select a card expense and a cash expense from different draft reports of the same submitter in Search, verify Merge is available.

  • As a non-admin approver, open a card expense on a submitted (processing) report, tap Merge — verify only other expenses on that same report appear.

  • As an admin who is also the submitter, tap Merge — verify all own eligible expenses appear (cross-report).

  • 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
  • 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 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 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)
  • 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)
  • 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.
  • 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
MacOS: Chrome / Safari

Remove the same-report shortcut for admins in getTransactionsForMerging.
Admins now discover cross-report and cross-workspace candidates via the
API (online) or the local filter (offline). Only non-admin managers
reviewing a processing report keep the same-report restriction.

The offline filter (getTransactionsForMergingLocally) now resolves admin
access per-candidate against that candidate's own workspace policy.
Candidates are excluded when their workspace policy is absent from the
local cache rather than assumed accessible.

MergeTransactionsListContent subscribes to allPolicies and allReports
and forwards them for the offline per-candidate check.

Tests: 5 new cases covering admin cross-report (same workspace),
non-admin workspace rejection, missing-cache exclusion, manager
same-report restriction, and admin-as-submitter cross-report.
@youssef-lr
youssef-lr requested review from a team as code owners September 12, 2026 22:45
@melvin-bot
melvin-bot Bot requested review from madmax330 and trjExpensify and removed request for a team September 12, 2026 22:45
@melvin-bot

melvin-bot Bot commented Sep 12, 2026

Copy link
Copy Markdown

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

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

Copy link
Copy Markdown

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: 354bee55b8

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

Comment on lines 243 to +245
areTransactionsEligibleForMerge(targetTransaction, transaction) &&
!isTransactionPendingDelete(transaction) &&
(isUnreportedExpense || (!!transaction.reportID && isMoneyRequestReportEligibleForMerge(transaction.reportID, isAdmin, rules)))
isMoneyRequestReportEligibleForMerge(candidateReport, isCandidateAdmin, rules)

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P1 Badge Keep offline merge candidates on the same submitter

When an offline admin has cached open reports for multiple employees, this filter accepts any candidate whose workspace grants admin access because neither areTransactionsEligibleForMerge() nor isMoneyRequestReportEligibleForMerge() compares the candidate report owner with the target report owner. This exposes expenses belonging to different employees as merge choices, despite isMergeActionForSelectedTransactions() explicitly rejecting that case in ReportSecondaryActionUtils.ts:862-885, and can initiate a destructive cross-user merge. Pass the target report into this filter and require matching ownerAccountID values (with the existing current-user rule for reported/unreported pairs).

Useful? React with 👍 / 👎.

@youssef-lr
youssef-lr marked this pull request as draft September 12, 2026 22:59
@codecov

codecov Bot commented Sep 15, 2026 •

Copy link
Copy Markdown

Codecov Report

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

Files with missing lines Coverage Δ
src/libs/actions/MergeTransaction.ts 90.56% <86.66%> (+10.96%) ⬆️
.../TransactionMerge/MergeTransactionsListContent.tsx 0.00% <0.00%> (ø)
... and 10 files with indirect coverage changes

@youssef-lr

Copy link
Copy Markdown
Contributor Author

Moved to #102438

@youssef-lr youssef-lr closed this Oct 5, 2026
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.

1 participant