Skip to content

Duplicate workspace#69146

Merged
mountiny merged 11 commits intoExpensify:mainfrom
callstack-internal:duplicate-workspace-v2
Sep 1, 2025
Merged

Duplicate workspace#69146
mountiny merged 11 commits intoExpensify:mainfrom
callstack-internal:duplicate-workspace-v2

Conversation

@narefyev91
Copy link
Contributor

@narefyev91 narefyev91 commented Aug 25, 2025

Explanation of Change

New feature from OldDot - Duplicate workspace

Fixed Issues

$ #67289
$ #69042
$ #69049
$ #69054
$ #69059
$ #69061
$ #69062
$ #69060
$ #69057
$ #69056
PROPOSAL:

Tests

Preconditions: Be sure that beta for duplicate workspace is enabled

  1. Go to Workspaces list
  2. Click on 3 dots on workspace in which you are admin
  3. Click on Duplicate workspace
  4. Verify that in the right panel Duplicate workspace fist step is opened with Avatar selector and pre-filled name (current workspace name (Duplicate).
  5. Verify that you could not proceed without workspace name
  6. Click next - verify that next step is shown with list and checkboxes
  7. Verify that you see correct information for each section (check design doc)
  8. Click Select All - verify that all items are selected, un check Select All - verify that all items are un selected
  9. Select All/ pick some items - click next - verify that modal is shown with correct information about workspace
  10. Click cancel - verify that modal is closed
  11. click proceed - verify that modal is closed, right panel is closed, on the workspace list new row is added - verify that it's highlighted (and scrolled to it if list with workspaces are long)
  12. Verify that selected features from step 9 also presented in the new workspace
  13. Verify that admin chat and expense chats are created as well
  • Verify that no errors appear in the JS console

Offline tests

  1. Go to Workspaces list
  2. Click on 3 dots on workspace in which you are admin
  3. Click on Duplicate workspace
  4. Verify that in the right panel Duplicate workspace fist step is opened with Avatar selector and pre-filled name (current workspace name (Duplicate).
  5. Verify that you could not proceed without workspace name
  6. Click next - verify that next step is shown with list and checkboxes
  7. Verify that you see correct information for each section (check design doc)
  8. Click Select All - verify that all items are selected, un check Select All - verify that all items are un selected
  9. Select All/ pick some items - click next - verify that modal is shown with correct information about workspace
  10. Click cancel - verify that modal is closed
  11. click proceed - verify that modal is closed, right panel is closed, on the workspace list new row is added - verify that it's highlighted (and scrolled to it if list with workspaces are long). Also verify that styles applies for offline row (same as in other places in the app)
  12. Verify that selected features from step 9 also presented in the new workspace

QA Steps

  1. Go to Workspaces list
  2. Click on 3 dots on workspace in which you are admin
  3. Click on Duplicate workspace
  4. Verify that in the right panel Duplicate workspace fist step is opened with Avatar selector and pre-filled name (current workspace name (Duplicate).
  5. Verify that you could not proceed without workspace name
  6. Click next - verify that next step is shown with list and checkboxes
  7. Verify that you see correct information for each section (check design doc)
  8. Click Select All - verify that all items are selected, un check Select All - verify that all items are un selected
  9. Select All/ pick some items - click next - verify that modal is shown with correct information about workspace
  10. Click cancel - verify that modal is closed
  11. click proceed - verify that modal is closed, right panel is closed, on the workspace list new row is added - verify that it's highlighted (and scrolled to it if list with workspaces are long)
  12. Verify that selected features from step 9 also presented in the new workspace
  13. Verify that admin chat and expense chats are created as well
  • 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 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
android-web.mov
iOS: Native
ios.mov
iOS: mWeb Safari
ios-web.mov
MacOS: Chrome / Safari
web.mov
MacOS: Desktop
desktop.mov

# Conflicts:
#	src/libs/actions/Policy/Policy.ts
#	src/pages/workspace/WorkspacesListPage.tsx
#	src/types/onyx/index.ts
@stitesExpensify stitesExpensify self-requested a review August 26, 2025 21:06
@github-actions
Copy link
Contributor

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

@mountiny mountiny requested a review from DylanDylann August 28, 2025 09:07
@narefyev91 narefyev91 marked this pull request as ready for review August 28, 2025 09:12
@narefyev91 narefyev91 requested a review from a team as a code owner August 28, 2025 09:12
@melvin-bot melvin-bot bot requested review from abdulrahuman5196 and removed request for a team August 28, 2025 09:12
@melvin-bot
Copy link

melvin-bot bot commented Aug 28, 2025

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

@github-actions
Copy link
Contributor

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

Android 🤖 iOS 🍎
https://ad-hoc-expensify-cash.s3.amazonaws.com/android/69146/index.html https://ad-hoc-expensify-cash.s3.amazonaws.com/ios/69146/index.html
Android iOS
Desktop 💻 Web 🕸️
https://ad-hoc-expensify-cash.s3.amazonaws.com/desktop/69146/NewExpensify.dmg https://69146.pr-testing.expensify.com
Desktop Web

👀 View the workflow run that generated this build 👀

@narefyev91 narefyev91 requested a review from a team as a code owner August 29, 2025 06:26
@JmillsExpensify
Copy link
Contributor

Looks good overall. This is pretty minor, though I think we should put Delete as the bottom option given that the list already is not in pure alphabetical order.
CleanShot 2025-08-29 at 13 46 01@2x

@narefyev91
Copy link
Contributor Author

@DylanDylann are we good here?

@DylanDylann
Copy link
Contributor

DylanDylann commented Sep 1, 2025

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
    • MacOS: Desktop
  • 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
  • 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
Android: mWeb Chrome
Screen.Recording.2025-08-15.at.11.56.29.mov
iOS: HybridApp
Screen.Recording.2025-08-15.at.12.01.38.mov
iOS: mWeb Safari
Screen.Recording.2025-08-15.at.11.57.58.mov
MacOS: Chrome / Safari
Screen.Recording.2025-08-15.at.11.54.09.mov
MacOS: Desktop
Screen.Recording.2025-08-15.at.11.58.46.mov

@DylanDylann
Copy link
Contributor

DylanDylann commented Sep 1, 2025

@stitesExpensify The additional change looks good to me. I reviewed the regressions and most of them seem to be BE bugs or expectation issues. Since this PR also includes the feature flag and is quite large, I’d prefer to merge it first and then address each regression separately.

@DylanDylann
Copy link
Contributor

@mountiny The avatar is not updated in the duplicated workspace (BE bug)

Screen.Recording.2025-09-01.at.19.40.35.mov

Copy link
Contributor

@mountiny mountiny left a comment

Choose a reason for hiding this comment

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

Alright, I think we will have 2 things to tackle after this change:

  • use only one read api call to get whatever data you might need to duplicate the policies, we cannot call N read commands, I dont know if you have raised this as an issue in the previous conversations, but remember this for future as it should have been raised
  • Handle the backTo routes, we should not be adding new backTo routes now

Comment on lines +1902 to +1909
WORKSPACE_DUPLICATE: {
route: 'workspace/:policyID/duplicate',
getRoute: (policyID: string, backTo?: string) => getUrlWithBackToParam(`workspace/${policyID}/duplicate`, backTo),
},
WORKSPACE_DUPLICATE_SELECT_FEATURES: {
route: 'workspace/:policyID/duplicate/select-features',
getRoute: (policyID: string, backTo?: string) => getUrlWithBackToParam(`workspace/${policyID}/duplicate/select-features`, backTo),
},
Copy link
Contributor

Choose a reason for hiding this comment

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

@narefyev91, we should not add new routes with backTo. Can you please refactor these flows so that they do not need the backTo param?

I dont want to block this on it, but let's follow up soon after this PR change

Comment on lines +204 to +216
const fetchWorkspaceRelatedData = useCallback(() => {
if (!policyID) {
return;
}
openWorkspaceMembersPage(policyID, Object.keys(allIds ?? {}));
openPolicyCategoriesPage(policyID);
openPolicyDistanceRatesPage(policyID);
openPolicyPerDiemPage(policyID);
openPolicyReportFieldsPage(policyID);
openPolicyTagsPage(policyID);
openPolicyTaxesPage(policyID);
openPolicyWorkflowsPage(policyID);
}, [policyID, allIds]);
Copy link
Contributor

Choose a reason for hiding this comment

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

We cannot do this @narefyev91 We need to call only one API per action.

What data is missing from your testing that you need to call all of the APIs - what about the OpenPolicyProfilePage does that not return what you need?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@mountiny here are the differences: - left (all apis), right (just OpenPolicyProfilePage)
Screenshot 2025-09-02 at 11 34 48
We missing Tags and Categories

Copy link
Contributor

Choose a reason for hiding this comment

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

Ok so it would be enough to call just the tags and categories, right? could you define it on the policy object data what exactly you are missing compared to OpenPolicyProfilePage to ensure the new API loads all you need

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@mountiny yeah - it will be good if we just add categories and tags - but i think we should not add those objects to policy? We should adjust a bit OpenPolicyProfilePage and include in it policyCategories_${policyID}, and policyTags_${policyID}
This what we have now for OpenPolicyProfilePage
Screenshot 2025-09-02 at 16 52 24

This is what we get for Categories API:
Screenshot 2025-09-02 at 16 52 55

This is what we get for Tags API:
Screenshot 2025-09-02 at 16 52 33

Copy link
Contributor

Choose a reason for hiding this comment

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

I think we just create a new API command like OpenPolicyDuplicatePage

Copy link
Contributor

Choose a reason for hiding this comment

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

@mountiny mountiny merged commit 9b05b4d into Expensify:main Sep 1, 2025
26 checks passed
@OSBotify
Copy link
Contributor

OSBotify commented Sep 2, 2025

🚀 Deployed to staging by https://github.com/mountiny in version: 9.2.1-0 🚀

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

@shawnborton
Copy link
Contributor

@narefyev91 can you confirm if this PR caused this regression here: #69845

@narefyev91
Copy link
Contributor Author

@narefyev91 can you confirm if this PR caused this regression here: #69845

yes

@OSBotify
Copy link
Contributor

OSBotify commented Sep 5, 2025

🚀 Deployed to production by https://github.com/arosiclair in version: 9.2.1-20 🚀

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

const [lastPaymentMethod] = useOnyx(ONYXKEYS.NVP_LAST_PAYMENT_METHOD, {canBeMissing: true});
const shouldShowLoadingIndicator = isLoadingApp && !isOffline;
const route = useRoute<PlatformStackRouteProp<AuthScreensParamList, typeof SCREENS.WORKSPACES_LIST>>();
const [duplicateWorkspace] = useOnyx(ONYXKEYS.DUPLICATE_WORKSPACE, {canBeMissing: false});
Copy link
Contributor

Choose a reason for hiding this comment

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

Seeing a console error on homepage: useOnyx returned no data for key with canBeMissing set to false for key duplicateWorkspace.

Copy link
Contributor

Choose a reason for hiding this comment

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

Should be fixed now!

...announceRoomChat.onyxSuccessData,
];

const failureData: OnyxUpdate[] = [
Copy link
Contributor

Choose a reason for hiding this comment

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

We haven't handled error state correctly which caused #70290.

key: `${ONYXKEYS.COLLECTION.POLICY}${targetPolicyID}`,
value: {
...policy,
areCategoriesEnabled: isCategoriesOptionSelected,
Copy link
Contributor

Choose a reason for hiding this comment

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

We should enable categories when duplicating a workspace, even if the user unchecks them, to match OD behavior
#72608

: undefined,
}
: undefined,
ratesCount > 0
Copy link
Contributor

Choose a reason for hiding this comment

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

This condition was not enough. We should also check areDistanceRatesEnabled.
Issue: #74469

@s77rt
Copy link
Member

s77rt commented Nov 27, 2025

@narefyev91 What's the point of this Overview being selectable? Is this supposed to affect what data we send to the backend? cc @mountiny @DylanDylann

Screenshot 2025-11-27 at 4 39 19 PM

(Coming from #74650)

@Pujan92
Copy link
Contributor

Pujan92 commented Dec 10, 2025

@narefyev91 could you plz help with the comment

@narefyev91
Copy link
Contributor Author

@narefyev91 could you plz help with the comment

It was part of design doc:
"Overview - Checks for any workspace description, default currency, and company address, e.g., “Sales team policy, USD currency, 2120 Hyde St, SF, 94109”"

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.