Skip to content

[Bulk workspace edits] Add Copy Policy Settings progress modal#91368

Merged
yuwenmemon merged 28 commits into
Expensify:mainfrom
fedirjh:copy-policy-settings-progress-modal
Jun 5, 2026
Merged

[Bulk workspace edits] Add Copy Policy Settings progress modal#91368
yuwenmemon merged 28 commits into
Expensify:mainfrom
fedirjh:copy-policy-settings-progress-modal

Conversation

@fedirjh

@fedirjh fedirjh commented May 21, 2026

Copy link
Copy Markdown
Contributor

Explanation of Change

Implements the Copy Policy Settings progress modal — task 6 of the Bulk Workspace Edits project. Stacked on top of #91241 (page 3 of 3) which is itself stacked on #90220 (page 2). Please land the upstream PRs first.

Fixed Issues

$ #88673
$ #92390
PROPOSAL: N/A

Tests

Setup

  1. Log in to NewDot as an admin of at least two Control workspaces (so the Copy settings flow is available from the workspace list three-dot menu).

Test 1 — Loading state

  1. From the Workspaces list, kick off a Copy settings flow and tap Copy settings on the Confirm step.
  2. Verify the Copy in progress modal appears with Let me know when it’s done.

Test 2 — Notification requested state

  1. From the loading state, tap Let me know when it’s done.
  2. Verify the modal transitions to the Concierge notification state.

Test 3 — Complete state (no notify requested)

  1. Reach the loading state (Test 1).
  2. Await for the copy to complete of Simulate backend completion: Onyx.merge('nvp_bulkPolicyCopySettings', {state: 'complete'}).
  3. Verify the modal updates to All Set! with a single Done button.
  4. Tap Done and confirm the modal is closed.
  • Verify that no errors appear in the JS console

Offline tests

N/A

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

Screenshot 2026-05-21 at 11 59 03 PM Screenshot 2026-05-21 at 11 59 07 PM
Android: Native
Android: mWeb Chrome
iOS: Native
iOS: mWeb Safari
MacOS: Chrome / Safari

fedirjh added 4 commits May 21, 2026 10:16
Adds translation keys for the copy-in-progress modal states:
copyInProgressTitle, copyInProgressDescription, letMeKnowPrompt,
conciergeNotificationTitle, conciergeNotificationDescription,
goToConcierge, dismiss, allSetTitle, allSetDescription, done.
…letion states

Uses ConfirmModal to display copy progress with three states:
- Loading: offers to notify user via Concierge when done
- Notification requested: shows confirmation and link to Concierge
- Complete: success state with dismiss action
Covers visibility, loading state transitions, notification request
flow, complete state, and state reset on step changes.
@melvin-bot

melvin-bot Bot commented May 21, 2026

Copy link
Copy Markdown

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

fedirjh added 7 commits May 21, 2026 23:27
…progress-modal

# Conflicts:
#	src/languages/de.ts
#	src/languages/en.ts
#	src/languages/es.ts
#	src/languages/fr.ts
#	src/languages/it.ts
#	src/languages/ja.ts
#	src/languages/nl.ts
#	src/languages/pl.ts
#	src/languages/pt-BR.ts
#	src/languages/zh-hans.ts
@codecov

codecov Bot commented May 21, 2026

Copy link
Copy Markdown

Codecov Report

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

Files with missing lines Coverage Δ
src/CONST/index.ts 93.79% <ø> (ø)
src/ONYXKEYS.ts 100.00% <ø> (ø)
src/components/ConfirmContent.tsx 89.09% <100.00%> (+0.41%) ⬆️
src/components/ConfirmModal.tsx 100.00% <ø> (ø)
src/libs/actions/Policy/CopyPolicySettings.ts 82.40% <100.00%> (+0.16%) ⬆️
src/pages/workspace/WorkspacesListPage.tsx 67.33% <100.00%> (+0.13%) ⬆️
...PolicySettings/CopyPolicySettingsProgressModal.tsx 100.00% <100.00%> (ø)
...ySettings/CopyPolicySettingsSelectFeaturesPage.tsx 71.11% <100.00%> (+71.11%) ⬆️
...pyPolicySettings/CopyPolicySettingsConfirmPage.tsx 0.00% <0.00%> (ø)
... and 40 files with indirect coverage changes

@fedirjh fedirjh requested review from francoisl and ishpaul777 May 21, 2026 23:16
@fedirjh fedirjh marked this pull request as ready for review May 21, 2026 23:16
@fedirjh fedirjh requested review from a team as code owners May 21, 2026 23:16
@melvin-bot melvin-bot Bot requested review from bernhardoj and joekaufmanexpensify and removed request for a team May 21, 2026 23:17
@melvin-bot

melvin-bot Bot commented May 21, 2026

Copy link
Copy Markdown

@bernhardoj 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 removed the request for review from a team May 21, 2026 23:17

@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: ee0f3c83d3

ℹ️ About Codex in GitHub

Your team has set up Codex to 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 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread src/pages/workspace/copyPolicySettings/CopyPolicySettingsProgressModal.tsx Outdated

@joekaufmanexpensify joekaufmanexpensify left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Core design doc issue

@francoisl francoisl requested a review from yuwenmemon May 24, 2026 22:46
@fedirjh fedirjh dismissed joekaufmanexpensify’s stale review May 26, 2026 18:51

The merge-base changed after approval.

@ishpaul777 ishpaul777 removed the request for review from bernhardoj May 28, 2026 14:47
@fedirjh

fedirjh commented Jun 4, 2026

Copy link
Copy Markdown
Contributor Author

Can we run an ad hoc build to test?

@dannymcclain Yes

@github-actions

github-actions Bot commented Jun 4, 2026

Copy link
Copy Markdown
Contributor

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

@github-actions

This comment has been minimized.

@dannymcclain

Copy link
Copy Markdown
Contributor

I think we should match the Select all control from Duplicate:

Duplicate This PR (Copy)
CleanShot 2026-06-04 at 09 51 07@2x CleanShot 2026-06-04 at 09 51 19@2x

I also didn't see the loader in the modal—and when I tried to go the Concierge route, when I clicked dismiss it popped up the confirmation screen as if I didn't choose the Concierge option. And then there's also a brief flicker at the end where the button changes to Yes and the modal has no other content.

CleanShot.2026-06-04.at.09.52.04.mp4
CleanShot 2026-06-04 at 09 55 54@2x

fedirjh added 3 commits June 4, 2026 16:41
Adds a new optional `isTitleLoading` prop to ConfirmModal and ConfirmContent
that displays an ActivityIndicator next to the title. This is useful for
modals showing progress states where a loading indicator in the header
area is more appropriate than the confirm button loading state.
…ismiss behavior

- Use new isTitleLoading prop to show loading indicator during copy in progress
- Fix "All Set" screen incorrectly showing when dismissing from Concierge
  notification step by only showing it when on the loading step AND backend
  reports complete
… page

Update CopyPolicySettingsSelectFeaturesPage to use custom Checkbox and
PressableWithFeedback for "Select all" control, matching the pattern used
in WorkspaceDuplicateSelectFeaturesForm for visual consistency.
@fedirjh

fedirjh commented Jun 4, 2026

Copy link
Copy Markdown
Contributor Author

I think we should match the Select all control from Duplicate:

@dannymcclain Updated to match that

Screenshot 2026-06-04 at 4 39 11 PM

I also didn't see the loader in the modal—and when I tried to go the Concierge route, when I clicked dismiss it popped up the confirmation screen as if I didn't choose the Concierge option. And then there's also a brief flicker at the end where the button changes to Yes and the modal has no other content.

Fixed that as well

CleanShot.2026-06-04.at.16.38.47.mp4
CleanShot.2026-06-04.at.16.45.54.mp4

@shubham1206agra

Copy link
Copy Markdown
Contributor

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 there are no new alerts related to the canBeMissing param for useOnyx
  • 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
  • xIf 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

Screen.Recording.2026-06-05.at.8.00.50.PM.mov
Screen.Recording.2026-06-05.at.9.03.21.PM.mov
Screen.Recording.2026-06-05.at.9.07.30.PM.mov

@yuwenmemon yuwenmemon merged commit d8f64dd into Expensify:main Jun 5, 2026
34 checks passed
@fedirjh fedirjh deleted the copy-policy-settings-progress-modal branch June 5, 2026 17:04
@OSBotify

OSBotify commented Jun 5, 2026

Copy link
Copy Markdown
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.

@github-actions

github-actions Bot commented Jun 5, 2026

Copy link
Copy Markdown
Contributor

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

@OSBotify

OSBotify commented Jun 5, 2026

Copy link
Copy Markdown
Contributor

🚀 Deployed to staging by https://github.com/yuwenmemon in version: 9.4.0-0 🚀

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

Bundle Size Analysis (Sentry):

@jponikarchuk

Copy link
Copy Markdown

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

@jponikarchuk

Copy link
Copy Markdown

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

@jponikarchuk

Copy link
Copy Markdown

Deploy Blocker #92873 was identified to be related to the PR #91368 that attempted to fix this issue.

@OSBotify

OSBotify commented Jun 9, 2026

Copy link
Copy Markdown
Contributor

🚀 Deployed to production by https://github.com/Julesssss in version: 9.4.0-7 🚀

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