Updates to leave or remove from workspace workflows by huult · Pull Request #58345 · Expensify/App

huult · 2025-03-13T05:37:33Z

Details

Fixed Issues

$ #56750
PROPOSAL: N/A

Tests

Same QA step

Verify that no errors appear in the JS console

Offline tests

QA Steps

Leaving a workspace

Set up cases:

If the person trying to leave is a member, prompt with an alert modal warning on clicking Leave.

Precondition: Member A is an Admin and invites Member B to the workspace with the role Member.

Steps:

Log in as Member B and go to Settings > Workspaces.
Click the three-dot menu next to the workspace.
Select "Leave".
Verify that a modal is displayed with the following template:

Leave workspace
If you leave this workspace, you won't be able to submit expenses to it.

[Leave workspace] <--- red button
[Cancel]

If the person trying to leave is an auditor, prompt with an alert modal warning on clicking Leave.

Precondition: Member A is an Admin and invites Member B to the workspace with the role Auditor.

Steps:

Log in as Member B and go to Settings > Workspaces.
Click the three-dot menu next to the workspace.
Select "Leave".
Verify that a modal is displayed with the following template:

Leave workspace
If you leave this workspace, you won't be able to view its reports and settings.

[Leave workspace] <--- red button
[Cancel]

If the person trying to leave is a non-owner admin, prompt with an alert modal warning on clicking Leave.

Precondition: Member A is an Admin and invites Member B to the workspace with the role Admin.

Steps:

Log in as Member B and go to Settings > Workspaces.
Click the three-dot menu next to the workspace.
Select "Leave".
Verify that a modal is displayed with the following template:

Leave workspace
If you leave this workspace, you won't be able to manage its settings.

[Leave workspace] <--- red button
[Cancel]

If the person trying to leave is an approver, prompt with an alert modal warning on clicking Leave

Precondition:

Member A is an Admin and invites Member B to the workspace
Member B is an approver in the workflow.

Steps:

Log in as Member B and go to Settings > Workspaces.
Click the three-dot menu next to the workspace.
Select "Leave".
Verify that a modal is displayed with the following template:

Leave workspace
If you leave this workspace, you'll be replaced in the approval workflow by [workspaceOwner], the workspace owner.

[Leave workspace] <--- red button
[Cancel]

If the person trying to leave is the technical contact, prompt with an alert modal warning on clicking Leave

Precondition:

Member A is an Admin and invites Member B to the workspace
Member B is set as the technical contact in OD

#56750 (comment)

Steps:

Log in as Member B and go to Settings > Workspaces.
Click the three-dot menu next to the workspace.
Select "Leave".
Verify that a modal is displayed with the following template:

Leave workspace
If you leave this workspace, you'll be replaced as the technical contact with [workspaceOwner], the workspace owner.

[Leave workspace] <--- red button
[Cancel]

If the person trying to leave is the preferred exporter, prompt with an alert modal warning on clicking Leave

Precondition:

Member B is the QBO config exporter

Steps:

Log in as Member B and go to Settings > Workspaces.
Click the three-dot menu next to the workspace.
Select "Leave".
Verify that a modal is displayed with the following template:

Leave workspace
If you leave this workspace, you'll be replaced as the preferred exporter with Anthony Davies, the workspace owner.

[Leave workspace] <--- red button
[Cancel]

If the person trying to leave has an outstanding processing report to action on:

Precondition:

Member A is an Admin and invites Member B to the workspace.
Member B is an approver in the workflow.
Member A creates an expense and submits it to Member B.

Steps:

Log in as Member B and go to Settings > Workspaces.
Click the three-dot menu next to the workspace.
Select "Leave".
Verify that a modal is displayed with the following template:

Leave workspace
Please approve any outstanding expense reports submitted to you before leaving the workspace.
[Got it] <--- Green button

If the person trying to leave is the reimburser, prompt with an alert modal warning on clicking Leave

Precondition:

Member B is the policy ACH account reimburser.

Steps:

Log in as Member B and go to Settings > Workspaces.
Click the three-dot menu next to the workspace.
Select "Leave".
Verify that a modal is displayed with the following template:

Leave workspace
You can't leave this workspace as the reimburser. Please set a new reimburser in Workspaces > Make or track payments, then try again.

[Got it] <--- green button

Removing someone from a workspace

If the person being removed is the preferred exporter, prompt with an alert modal warning on clicking Remove from workspace.

Precondition:

Member B is the QBO config exporter

Log in as Member B and Go to Settings > Workspace > Members
Click on the member row
Click "Remove from workspace"
Verify that a modal is displayed with the following template:

Remove from workspace
If you remove Bob Williams from this workspace, we'll replace them as the preferred exporter with Anthony Davies, the workspace owner. You can change the preferred exporter in Accounting > Export.

[Remove] <--- red button
[Cancel]

If the person being removed is the reimburser, prompt with an alert modal warning on clicking Remove from workspace.

Precondition:

Member B is the policy ACH account reimburser.

Log in as Member B and Go to Settings > Workspace > Members
Click on the member row
Click "Remove from workspace"
Verify that a modal is displayed with the following template:

Remove from workspace
You can't remove Bob Williams from this workspace. Please set a new reimburser in Workflows > Make or track payments, then try again.

[Got it] <--- green button

If the person being removed is an approver, prompt with an alert modal warning on clicking Remove from workspace

Precondition:

Member A is an Admin and invites Member B to the workspace
Member B is an approver in the workflow.

Log in as Member B and Go to Settings > Workspace > Members
Click on the member row
Click "Remove from workspace"
Verify that a modal is displayed with the following template:

Remove from workspace
If you remove Bob Williams from this workspace, we'll replace them in the approval workflow with Anthony Davies, the workspace owner.

[Remove] <--- red button
[Cancel]

If the person being removed is the technical contact, prompt with an alert modal warning on clicking Remove from workspace.

Precondition:

Member A is an Admin and invites Member B to the workspace
Member B is set as the technical contact in OD

Log in as Member B and Go to Settings > Workspace > Members
Click on the member row
Click "Remove from workspace"
Verify that a modal is displayed with the following template:

Remove from workspace
If you remove Bob Williams from this workspace, we'll replace them as the technical contact with Anthony Davies, the workspace owner.

[Remove] <--- red button
[Cancel]

Verify that no errors appear in the JS console

PR Author Checklist

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

If the person trying to leave is a member, prompt with an alert modal warning on clicking Leave.

Screen.Recording.2025-05-13.at.12.53.10.mp4

If the person trying to leave is an auditor, prompt with an alert modal warning on clicking Leave.

Screen.Recording.2025-05-13.at.12.54.29.mp4

If the person trying to leave is a non-owner admin, prompt with an alert modal warning on clicking Leave.

Screen.Recording.2025-05-13.at.12.56.40.mp4

If the person trying to leave is an approver, prompt with an alert modal warning on clicking Leave

Screen.Recording.2025-05-13.at.12.58.37.mp4

If the person trying to leave is the technical contact, prompt with an alert modal warning on clicking Leave

Screen.Recording.2025-05-13.at.13.10.03.mp4

If the person trying to leave is the preferred exporter, prompt with an alert modal warning on clicking Leave

Screen.Recording.2025-05-22.at.11.24.58.mov

If the person being removed is the preferred exporter, prompt with an alert modal warning on clicking Remove from workspace.

Screen.Recording.2025-05-22.at.11.29.07.mp4

If the person trying to leave has an outstanding processing report to action on:

Screen.Recording.2025-07-02.at.12.42.08.mov

If the person being removed has an outstanding processing report to action on:

Screen.Recording.2025-07-02.at.12.41.55.mov

If the person trying to leave is the reimburser, prompt with an alert modal warning on clicking Leave

Screen.Recording.2025-05-22.at.11.06.27.mov

If the person being removed is the reimburser, prompt with an alert modal warning on clicking Remove from workspace.

Screen.Recording.2025-05-22.at.11.05.32.mov

If the person being removed is an approver, prompt with an alert modal warning on clicking Remove from workspace

Screen.Recording.2025-05-13.at.13.18.28.mp4

If the person being removed is the technical contact, prompt with an alert modal warning on clicking Remove from workspace.

Screen.Recording.2025-05-13.at.13.38.22.mp4

Any user on a domain which has "prevent workspace creation/removal" enabled.

Skip

MacOS: Desktop

MonilBhavsar · 2025-03-27T19:05:38Z

@huult there are conflicts. If you could please fix

…ve-workspace-restrictions

huult · 2025-03-28T02:17:54Z

@MonilBhavsar it's done

MonilBhavsar · 2025-03-28T21:35:55Z

Thank you!

MonilBhavsar · 2025-04-02T06:50:56Z

#56750 (comment)

MonilBhavsar · 2025-04-07T19:33:46Z

#56750 (comment)

…ve-workspace-restrictions

MonilBhavsar

I see you have added TECHNICAL_CONTACT as a new Onyx key. But it's not an onyx key. It's just an object key in policy_ Onyx collection

huult · 2025-05-02T07:40:13Z

@MonilBhavsar thanks, i will update it

huult · 2025-05-06T03:51:18Z

@MonilBhavsar Is your PR already merged?

MonilBhavsar · 2025-05-06T04:44:21Z

Yes, it was deployed

…ve-workspace-restrictions

huult · 2025-05-13T06:44:29Z

@MonilBhavsar @trjExpensify

I've finished implementing the code for this ticket and tested some cases, but I'm not sure how to test the ones listed below. Could you help me? For the tests I've completed, you can refer to the MacOS: Chrome / Safari section in Screenshots/Videos

If the person being removed is the preferred exporter, prompt with an alert modal warning on clicking Remove from workspace.
If the person being removed is the reimburser, prompt with an alert modal warning on clicking Remove from workspace.
If the person trying to leave is the reimburser, prompt with an alert modal warning on clicking Leave
If the person being removed has an outstanding processing report to action on:
If the person trying to leave has an outstanding processing report to action on:
If the person trying to leave is the preferred exporter, prompt with an alert modal warning on clicking Leave
If the person trying to leave is the reimburser, prompt with an alert modal warning on clicking Leave

trjExpensify · 2025-05-14T01:04:58Z

If the person being removed is the preferred exporter, prompt with an alert modal warning on clicking Remove from workspace.
If the person trying to leave is the preferred exporter, prompt with an alert modal warning on clicking Leave

You'll need to connect a workspace to an integration, like QBO, and set a user as the preferred exporter in the settings. Then, try to remove that user, or leave. @shubham1206agra is the C+ on the issue to this PR, perhaps he can help here.

If the person being removed is the reimburser, prompt with an alert modal warning on clicking Remove from workspace.
If the person trying to leave is the reimburser, prompt with an alert modal warning on clicking Leave

You'll need to add a business bank account to the workspace in Workflows, and set a user as the reimburser in the settings once connected. Then, try to remove that user, or leave. You can use the test credentials from here.

If the person being removed has an outstanding processing report to action on:
If the person trying to leave has an outstanding processing report to action on:

Have userA submit a report to userB, then as userB try to leave the workspace or remove userB from the workspace.

huult · 2025-05-14T02:18:10Z

@trjExpensify thank you so much

shubham1206agra · 2025-05-19T05:33:09Z

You'll need to connect a workspace to an integration, like QBO, and set a user as the preferred exporter in the settings. Then, try to remove that user, or leave. @shubham1206agra is the C+ on the issue to this PR, perhaps he can help here.

@huult Send me your email and I will add you to a workspace

…ve-workspace-restrictions

src/pages/workspace/WorkspacesListPage.tsx

shubham1206agra · 2025-10-30T16:08:40Z

If the person trying to leave is a member, prompt with an alert modal warning on clicking Leave.

Pass

If the person trying to leave is an auditor, prompt with an alert modal warning on clicking Leave.

Pass

If the person trying to leave is a non-owner admin, prompt with an alert modal warning on clicking Leave.

Pass

If the person trying to leave is an approver, prompt with an alert modal warning on clicking Leave

Pass (without default approver)

Note

@trjExpensify How do we need to handle default approver? As for this case, leave button is disabled before this PR.

Note

@MonilBhavsar OpenApp is not sending default approver + approver workflow in the policy data. Can you please fix this?

If the person being removed is an approver, prompt with an alert modal warning on clicking Remove from workspace.

Pass

If the person trying to leave has an outstanding processing report to action on:

Pass

If the person being removed has an outstanding processing report to action on:

Pass

Screen.Recording.2025-10-30.at.9.31.36.PM.mov

If the person trying to leave is the reimburser, prompt with an alert modal warning on clicking Leave

Pass (See Note)

Note

@MonilBhavsar OpenApp is not sending reimburser in the policy data. Can you please fix this?

If the person being removed is the reimburser, prompt with an alert modal warning on clicking Remove from workspace.

Pass

If the person trying to leave is the technical contact, prompt with an alert modal warning on clicking Leave

Pass (See Note)

Note

@MonilBhavsar OpenApp is not sending technical contact in the policy data. Can you please fix this?

If the person being removed is the technical contact, prompt with an alert modal warning on clicking Remove from workspace.

Pass

If the person trying to leave is the preferred exporter, prompt with an alert modal warning on clicking Leave

Pass (See Note)

Note

@MonilBhavsar OpenApp is not sending preferred exporter in the policy data. Can you please fix this?

If the person being removed is the preferred exporter, prompt with an alert modal warning on clicking Remove from workspace.

Pass

trjExpensify · 2025-10-30T16:58:54Z

@trjExpensify How do we need to handle default approver? As for this case, leave button is disabled before this PR.

If the default approver is the workspace owner, they can't leave/be removed. If it's not, then it's this one and we set the workspace owner as the default approver:

If the person trying to leave is an approver, prompt with an alert modal warning on clicking Leave

Leave workspace
If you leave this workspace, you'll be replaced in the approval workflow by Anthony Davies, the workspace owner.

[Leave workspace] <--- red button
[Cancel]

If the person being removed is an approver, prompt with an alert modal warning on clicking Remove from workspace.

Remove from workspace
If you remove Bob Williams from this workspace, we'll replace them in the approval workflow with Anthony Davies, the workspace owner.

[Remove] <--- red button
[Cancel]

…ve-workspace-restrictions

src/pages/workspace/WorkspaceOverviewPage.tsx

src/pages/workspace/WorkspacesListPage.tsx

shubham1206agra · 2025-10-31T10:10:41Z

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

MonilBhavsar

Thanks all! 🙇

OSBotify · 2025-10-31T12:16:04Z

✋ 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 · 2025-10-31T21:45:50Z

🚀 Deployed to staging by https://github.com/MonilBhavsar in version: 9.2.42-0 🚀

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

OSBotify · 2025-11-03T22:39:03Z

🚀 Deployed to production by https://github.com/luacmartins in version: 9.2.42-11 🚀

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

linhvovan29546 · 2025-11-10T09:38:19Z

src/languages/es.ts

        expenseReports: 'Informes de Gastos',
        rateOutOfPolicy: 'Tasa fuera de póliza',
+        leaveWorkspace: 'Salir del espacio de trabajo',
+        leaveWorkspaceConfirmation: 'Si sales de este espacio de trabajo, no podrás enviar gastos en él',


This text is missing a period at the end of the sentence, which caused this issue. We've applied the fix here

eVoloshchak · 2025-12-07T20:49:45Z

src/pages/workspace/members/WorkspaceMemberDetailsPage.tsx

+            policy?.connections?.quickbooksDesktop?.config?.export?.exporter,
+            policy?.connections?.quickbooksOnline?.config?.export?.exporter,
+            policy?.connections?.xero?.config?.export?.exporter,
+            policy?.connections?.netsuite?.options.config.exporter,


👋 Hey, coming from #74903.
This has caused a crash when trying to connect to NetSuite with incorrect credentials, we were missing optional chaining for netsuite exporter

policy?.connections?.netsuite?.options?.config?.exporter,

huult added 2 commits March 13, 2025 11:52

handle leave workspace

025ff2f

handle remove member from workspace

4ba8bf7

huult requested a review from a team as a code owner March 13, 2025 05:37

huult mentioned this pull request Mar 13, 2025

[Due for Payment 11th Nov] [CMB] Implement the proper handling of restrictions to leave or be removed from a workspace in NewDot #56750

Closed

8 tasks

fix lint

dea7535

MonilBhavsar self-requested a review March 26, 2025 06:19

Merge remote-tracking branch 'upstream/main' into 56750-leave-or-remo…

6d95cbb

…ve-workspace-restrictions

huult added 3 commits April 29, 2025 15:37

Merge remote-tracking branch 'upstream/main' into 56750-leave-or-remo…

41b8d59

…ve-workspace-restrictions

Merge remote-tracking branch 'upstream/main' into 56750-leave-or-remo…

6d698d1

…ve-workspace-restrictions

update leave confirm for technical contact

8df0ba7

MonilBhavsar reviewed May 2, 2025

View reviewed changes

huult added 7 commits May 8, 2025 22:40

Merge remote-tracking branch 'upstream/main' into 56750-leave-or-remo…

3bb4d19

…ve-workspace-restrictions

Merge remote-tracking branch 'upstream/main' into 56750-leave-or-remo…

dc75527

…ve-workspace-restrictions

update case technical contact

fae4964

update policy type

4b747d3

Merge remote-tracking branch 'upstream/main' into 56750-leave-or-remo…

6efdcdf

…ve-workspace-restrictions

update translation

31b1a8b

update case remove technical contact

5f3bc9b

huult added 3 commits October 30, 2025 21:58

remove breakline

3a21f67

Merge remote-tracking branch 'upstream/main' into 56750-leave-or-remo…

f842242

…ve-workspace-restrictions

remove code unused

cf388d6

shubham1206agra reviewed Oct 30, 2025

View reviewed changes

src/pages/workspace/WorkspacesListPage.tsx Outdated Show resolved Hide resolved

update dependencies

a6ce55e

huult added 2 commits October 31, 2025 08:00

Merge remote-tracking branch 'upstream/main' into 56750-leave-or-remo…

39ff223

…ve-workspace-restrictions

Merge remote-tracking branch 'upstream/main' into 56750-leave-or-remo…

49e1c51

…ve-workspace-restrictions

shubham1206agra reviewed Oct 31, 2025

View reviewed changes

src/pages/workspace/WorkspaceOverviewPage.tsx Outdated Show resolved Hide resolved

shubham1206agra reviewed Oct 31, 2025

View reviewed changes

src/pages/workspace/WorkspacesListPage.tsx Outdated Show resolved Hide resolved

huult added 2 commits October 31, 2025 14:33

remove check default approver

c63bd62

remove code unused

6648da8

shubham1206agra approved these changes Oct 31, 2025

View reviewed changes

melvin-bot bot requested a review from MonilBhavsar October 31, 2025 10:11

MonilBhavsar approved these changes Oct 31, 2025

View reviewed changes

MonilBhavsar merged commit 67060b1 into Expensify:main Oct 31, 2025
27 checks passed

OSBotify mentioned this pull request Oct 31, 2025

Deploy Checklist: New Expensify 2025-10-31 #73985

Closed

This was referenced Nov 1, 2025

[Due for payment 2025-11-11] Workspace - Confirm modal title is Leave when leaving workspace from Overview #74002

Closed

Workspace- Error when leaving workspace as ex workspace owner who is part of approval workflow #74003

Closed

lanitochka17 mentioned this pull request Nov 1, 2025

[Due for payment 2025-11-11] Workspace - Screen Freezes when clicking leave #74042

Closed

16 tasks

jponikarchuk mentioned this pull request Nov 3, 2025

Workflow - The pop-up display the wrong sentence and button when approver leave WS #74072

Closed

8 tasks

This was referenced Nov 3, 2025

iOS - Workspace - Member not able to leave WS via 3 dot menu, when re-invited, Not here page opens #74039

Closed

Revert "Updates to leave or remove from workspace workflows" #74075

Closed

linhvovan29546 reviewed Nov 10, 2025

View reviewed changes

eVoloshchak reviewed Dec 7, 2025

View reviewed changes

Conversation

huult commented Mar 13, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Details

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

Uh oh!

MonilBhavsar commented Mar 27, 2025

Uh oh!

huult commented Mar 28, 2025

Uh oh!

MonilBhavsar commented Mar 28, 2025

Uh oh!

MonilBhavsar commented Apr 2, 2025

Uh oh!

MonilBhavsar commented Apr 7, 2025

Uh oh!

MonilBhavsar left a comment

Choose a reason for hiding this comment

Uh oh!

huult commented May 2, 2025

Uh oh!

huult commented May 6, 2025

Uh oh!

MonilBhavsar commented May 6, 2025

Uh oh!

huult commented May 13, 2025

Uh oh!

trjExpensify commented May 14, 2025

Uh oh!

huult commented May 14, 2025

Uh oh!

shubham1206agra commented May 19, 2025

Uh oh!

Uh oh!

shubham1206agra commented Oct 30, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

trjExpensify commented Oct 30, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Uh oh!

Uh oh!

shubham1206agra commented Oct 31, 2025

Reviewer Checklist

Uh oh!

MonilBhavsar left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

OSBotify commented Oct 31, 2025

Uh oh!

OSBotify commented Oct 31, 2025

Uh oh!

OSBotify commented Nov 3, 2025

Uh oh!

linhvovan29546 Nov 10, 2025

Choose a reason for hiding this comment

Uh oh!

eVoloshchak Dec 7, 2025

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

7 participants

huult commented Mar 13, 2025 •

edited

Loading

shubham1206agra commented Oct 30, 2025 •

edited

Loading

trjExpensify commented Oct 30, 2025 •

edited

Loading