Skip to content

feat: Handle the REJECTEDTOSUBMITTER#84053

Merged
lakchote merged 9 commits intoExpensify:mainfrom
truph01:feat/82793-release-1
Mar 5, 2026
Merged

feat: Handle the REJECTEDTOSUBMITTER#84053
lakchote merged 9 commits intoExpensify:mainfrom
truph01:feat/82793-release-1

Conversation

@truph01
Copy link
Contributor

@truph01 truph01 commented Mar 3, 2026

Explanation of Change

  • This PR extends existing REJECTED handling so REJECTEDTOSUBMITTER is rendered properly.

Fixed Issues

$ #82793
PROPOSAL:

Tests

  1. Create a corporate workspace. User A is admin, user B is employee
  2. In ND, as user B, Submit a report to user A
  3. In OD, as user A, reject the report
  4. Copy the link of the report from OldDot and navigate to it in NewDot directly
  5. Make sure the rejected this report report action is showing.
  • Verify that no errors appear in the JS console

Offline tests

QA Steps

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

  • 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 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: mWeb Chrome
iOS: Native
iOS: mWeb Safari
MacOS: Chrome / Safari
Screen.Recording.2026-03-03.at.23.49.33.mov

@truph01 truph01 requested review from a team as code owners March 3, 2026 16:56
@melvin-bot melvin-bot bot requested review from linhvovan29546 and removed request for a team March 3, 2026 16:56
@melvin-bot
Copy link

melvin-bot bot commented Mar 3, 2026

@linhvovan29546 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 trjExpensify and removed request for a team March 3, 2026 16:56
@lakchote lakchote self-requested a review March 3, 2026 16:59
lastMessageTextFromReport = translate('iou.forwarded');
}
} else if (lastReportAction?.actionName === CONST.REPORT.ACTIONS.TYPE.REJECTED) {
} else if (lastReportAction?.actionName === CONST.REPORT.ACTIONS.TYPE.REJECTED || lastReportAction?.actionName === CONST.REPORT.ACTIONS.TYPE.REJECTED_TO_SUBMITTER) {
Copy link
Contributor

Choose a reason for hiding this comment

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

❌ CONSISTENCY-3 (docs)

The compound check actionName === CONST.REPORT.ACTIONS.TYPE.REJECTED || actionName === CONST.REPORT.ACTIONS.TYPE.REJECTED_TO_SUBMITTER is duplicated in 4 files (OptionsListUtils/index.ts, ReportNameUtils.ts, ContextMenuActions.tsx, PureReportActionItem.tsx). The codebase already has a well-established convention for this in ReportActionsUtils.ts with helpers like isApprovedAction, isForwardedAction, isRetractedAction, etc. A centralized isRejectedAction helper would follow that pattern and prevent future drift if more rejected-type actions are added.

Create an isRejectedAction helper in src/libs/ReportActionsUtils.ts and use it across all 4 call sites:

// In src/libs/ReportActionsUtils.ts
function isRejectedAction(
    reportAction: OnyxInputOrEntry<ReportAction>,
): boolean {
    return isActionOfType(reportAction, CONST.REPORT.ACTIONS.TYPE.REJECTED, CONST.REPORT.ACTIONS.TYPE.REJECTED_TO_SUBMITTER);
}

Then replace all 4 occurrences with e.g.:

ReportActionsUtils.isRejectedAction(lastReportAction)

Please rate this suggestion with 👍 or 👎 to help us improve! Reactions are used to monitor reviewer efficiency.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@MelvinBot Apply this feedback

Copy link
Contributor

Choose a reason for hiding this comment

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

Applied! Created isRejectedAction helper in ReportActionsUtils.ts and replaced all 4 duplicated compound checks with it. See ac8a829.

MelvinBot and others added 2 commits March 3, 2026 17:10
Create a centralized isRejectedAction helper in ReportActionsUtils.ts
that checks for both REJECTED and REJECTED_TO_SUBMITTER action types,
replacing the duplicated compound checks across 4 files.

Co-authored-by: truph01 <truph01@users.noreply.github.com>
Copy link
Contributor

@trjExpensify trjExpensify left a comment

Choose a reason for hiding this comment

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

Why can't this just read "rejected" like others? (i.e "submitted")

Image

I can't see "this report" in the doc mocks:

Image

@melvin-bot
Copy link

melvin-bot bot commented Mar 4, 2026

Hey, I noticed you changed src/languages/en.ts in a PR from a fork. For security reasons, translations are not generated automatically for PRs from forks.

If you want to automatically generate translations for other locales, an Expensify employee will have to:

  1. Look at the code and make sure there are no malicious changes.
  2. Run the Generate static translations GitHub workflow. If you have write access and the K2 extension, you can simply click: [this button]

Alternatively, if you are an external contributor, you can run the translation script locally with your own OpenAI API key. To learn more, try running:

npx ts-node ./scripts/generateTranslations.ts --help

Typically, you'd want to translate only what you changed by running npx ts-node ./scripts/generateTranslations.ts --compare-ref main

@linhvovan29546
Copy link
Contributor

linhvovan29546 commented Mar 4, 2026

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
Screen.Recording.2026-03-04.at.09.58.27.mov
Android: mWeb Chrome Screenshot_1772593341
iOS: HybridApp Simulator Screenshot - iPhone 16 Pro Max - 2026-03-04 at 09 37 20
iOS: mWeb Safari
Screen.Recording.2026-03-04.at.09.30.06.mov
MacOS: Chrome / Safari
Screen.Recording.2026-03-04.at.09.19.32.mov

@codecov
Copy link

codecov bot commented Mar 4, 2026

Codecov Report

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

Files with missing lines Coverage Δ
src/libs/OptionsListUtils/index.ts 80.18% <100.00%> (ø)
src/libs/ReportActionsUtils.ts 53.50% <100.00%> (+0.04%) ⬆️
src/libs/ReportNameUtils.ts 81.09% <100.00%> (ø)
src/libs/actions/IOU/index.ts 73.07% <ø> (ø)
...es/inbox/report/ContextMenu/ContextMenuActions.tsx 25.49% <100.00%> (ø)
src/pages/inbox/report/PureReportActionItem.tsx 56.48% <100.00%> (ø)
... and 13 files with indirect coverage changes

@linhvovan29546
Copy link
Contributor

@MelvinBot Add unit tests for isRejectedAction and update ReportUtilsTest to include the new actionName REJECTED_TO_SUBMITTER.

@MelvinBot
Copy link
Contributor

I reviewed the request to add unit tests for isRejectedAction and update ReportUtilsTest to include REJECTED_TO_SUBMITTER.

However, I can't push code changes to this PR because I didn't open it and I'm not listed as an assignee. Here's exactly what needs to be added:


1. Add isRejectedAction tests in tests/unit/ReportActionsUtilsTest.ts

Add this describe block (e.g., after the isDeletedAction block around line 1742):

describe('isRejectedAction', () => {
    it('should return true for REJECTED action type', () => {
        // Given a report action with REJECTED action type
        const action: ReportAction<typeof CONST.REPORT.ACTIONS.TYPE.REJECTED> = {
            ...createRandomReportAction(0),
            actionName: CONST.REPORT.ACTIONS.TYPE.REJECTED,
            created: '2025-11-21',
            reportActionID: '1',
            originalMessage: undefined,
            message: [],
            previousMessage: [],
        };

        // When checking if the action is a rejected action
        const result = ReportActionsUtils.isRejectedAction(action);

        // Then it should return true
        expect(result).toBe(true);
    });

    it('should return true for REJECTED_TO_SUBMITTER action type', () => {
        // Given a report action with REJECTED_TO_SUBMITTER action type
        const action: ReportAction<typeof CONST.REPORT.ACTIONS.TYPE.REJECTED_TO_SUBMITTER> = {
            ...createRandomReportAction(0),
            actionName: CONST.REPORT.ACTIONS.TYPE.REJECTED_TO_SUBMITTER,
            created: '2025-11-21',
            reportActionID: '1',
            originalMessage: undefined,
            message: [],
            previousMessage: [],
        };

        // When checking if the action is a rejected action
        const result = ReportActionsUtils.isRejectedAction(action);

        // Then it should return true because REJECTED_TO_SUBMITTER is also a rejected action
        expect(result).toBe(true);
    });

    it('should return false for non-rejected action type', () => {
        // Given a report action with SUBMITTED action type (not rejected)
        const action: ReportAction<typeof CONST.REPORT.ACTIONS.TYPE.SUBMITTED> = {
            ...createRandomReportAction(0),
            actionName: CONST.REPORT.ACTIONS.TYPE.SUBMITTED,
            created: '2025-11-21',
            reportActionID: '1',
            originalMessage: {
                amount: 10000,
                currency: 'USD',
            },
            message: [],
            previousMessage: [],
        };

        // When checking if the action is a rejected action
        const result = ReportActionsUtils.isRejectedAction(action);

        // Then it should return false
        expect(result).toBe(false);
    });

    it('should return false for null action', () => {
        // Given a null action

        // When checking if the action is a rejected action
        const result = ReportActionsUtils.isRejectedAction(null);

        // Then it should return false because the action is null
        expect(result).toBe(false);
    });
});

2. Add REJECTED_TO_SUBMITTER test in tests/unit/ReportUtilsTest.ts

Add this test right after the existing 'should return rejected action name' test (after line 2379):

test('should return rejected action name for REJECTED_TO_SUBMITTER', () => {
    const rejectedToSubmitterAction: ReportAction = {
        ...baseParentReportAction,
        actionName: CONST.REPORT.ACTIONS.TYPE.REJECTED_TO_SUBMITTER,
    };

    const threadReport: Report = {
        ...baseExpenseReport,
        parentReportID: baseChatReport.reportID,
        parentReportActionID: rejectedToSubmitterAction.reportActionID,
    };

    const reportActions = {
        [`${ONYXKEYS.COLLECTION.REPORT_ACTIONS}${threadReport.parentReportID}`]: {[rejectedToSubmitterAction.reportActionID]: rejectedToSubmitterAction},
    };
    const reportName = computeReportName(threadReport, undefined, undefined, undefined, undefined, participantsPersonalDetails, reportActions);

    expect(reportName).toBe('rejected');
});

⚠️ I can't push changes to this PR because I didn't open it and I'm not listed as an assignee. To have me make these changes directly, add me to the PR assignees and then retry your request.

@linhvovan29546
Copy link
Contributor

@truph01 Could you please add the unit tests?

lakchote
lakchote previously approved these changes Mar 4, 2026
Copy link
Contributor

@lakchote lakchote left a comment

Choose a reason for hiding this comment

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

LGTM, @trjExpensify want to give it a final look?

trjExpensify
trjExpensify previously approved these changes Mar 4, 2026
Copy link
Contributor

@trjExpensify trjExpensify left a comment

Choose a reason for hiding this comment

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

The sys message looks good now. 👍

@linhvovan29546
Copy link
Contributor

@truph01 there's a merge conflict now.

@truph01 truph01 dismissed stale reviews from trjExpensify and lakchote via d6e3c19 March 5, 2026 02:21
@truph01
Copy link
Contributor Author

truph01 commented Mar 5, 2026

There are a lot of Eslint errors that aren't related to this PR.

@linhvovan29546
Copy link
Contributor

@truph01 I don't see that ESLint error on main. Do you know why it's only appearing on this PR?

@truph01
Copy link
Contributor Author

truph01 commented Mar 5, 2026

@truph01 I don't see that ESLint error on main. Do you know why it's only appearing on this PR?

@linhvovan29546 I think it’s because the linter runs against all files changed in this PR, which is why the error is appearing here but not on main.

@linhvovan29546
Copy link
Contributor

I didn't see this ESLint error before the conflict appeared, so a recent PR merged to main probably triggered it. But I can't find which one

@linhvovan29546
Copy link
Contributor

That came from #83798

@melvin-bot melvin-bot bot requested a review from lakchote March 5, 2026 09:28
Copy link
Contributor

@lakchote lakchote left a comment

Choose a reason for hiding this comment

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

LGTM

@lakchote lakchote merged commit 36e3acf into Expensify:main Mar 5, 2026
29 of 31 checks passed
@OSBotify
Copy link
Contributor

OSBotify commented Mar 6, 2026

🚀 Deployed to staging by https://github.com/lakchote in version: 9.3.32-0 🚀

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

@jponikarchuk
Copy link

Deploy Blocker #84384 was identified to be related to this PR.
I can't find Ad-hoc build in this PR. Issue is reproducible in next PR build and not reproducible in previous PR build

@OSBotify
Copy link
Contributor

OSBotify commented Mar 6, 2026

🚀 Deployed to production by https://github.com/blimpich in version: 9.3.32-3 🚀

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.

7 participants