Skip to content

Load full report when admins open a room from the Workspace Rooms list#93795

Merged
grgia merged 3 commits into
Expensify:mainfrom
software-mansion-labs:sumo-slonik/fix/93248-rooms-admin-join-invite
Jul 16, 2026
Merged

Load full report when admins open a room from the Workspace Rooms list#93795
grgia merged 3 commits into
Expensify:mainfrom
software-mansion-labs:sumo-slonik/fix/93248-rooms-admin-join-invite

Conversation

@sumo-slonik

@sumo-slonik sumo-slonik commented Jun 17, 2026

Copy link
Copy Markdown
Contributor

Explanation of Change

Admins open the report details RHP directly from the Workspace Rooms list, skipping the openReport call that ReportScreen normally makes — so the RHP operated on the stub report loaded for the list and Join (member count dropped to 0), Invite and renaming broke. We now fetch the full report before navigating, so those actions run against complete data.

Fixed Issues

$ #93248
PROPOSAL:

Tests

  1. Precondition: a workspace with an invited member, and the workspaceRoomsPage beta enabled.
  2. As the member, open FAB → Start chat → Room and create a room under that workspace.
  3. As an admin (not yet a member of that room), go to Workspace settings → Rooms.
  4. Click the room created by the member → the report details RHP opens.
  5. Click Join → verify you join the room and the member count increases (it does not drop to 0).
  6. Open the room again → Members → Invite member → invite a member → go back to Members → verify the invited member is listed and no error is shown.
  7. Change the room name / room settings → verify the change saves successfully.
  8. Verify that no errors appear in the JS console.
  • Verify that no errors appear in the JS console

Offline tests

N/A — the change only affects how an admin opens an existing room (an extra report fetch before navigation); there is no offline-specific behavior to verify.

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

MacOS: Chrome / Safari
final_admin_test.mp4

Admins open the report details RHP directly from the Workspace Rooms list
instead of the room report, which skipped the openReport call ReportScreen
makes. The RHP then operated on the stub report loaded for the list, breaking
Join (member count dropped to 0), Invite and renaming. Fetch the full report
when navigating so these actions run against complete data.

Fixes Expensify#93248
@codecov

codecov Bot commented Jun 17, 2026

Copy link
Copy Markdown

Codecov Report

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

Files with missing lines Coverage Δ
src/libs/actions/Report/index.ts 71.18% <100.00%> (+0.55%) ⬆️
src/pages/workspace/rooms/WorkspaceRoomsPage.tsx 0.00% <0.00%> (ø)
... and 16 files with indirect coverage changes

@sumo-slonik
sumo-slonik marked this pull request as ready for review June 17, 2026 12:07
@sumo-slonik
sumo-slonik requested review from a team as code owners June 17, 2026 12:07
@melvin-bot
melvin-bot Bot requested review from gijoe0295 and trjExpensify and removed request for a team June 17, 2026 12:07
@melvin-bot

melvin-bot Bot commented Jun 17, 2026

Copy link
Copy Markdown

@gijoe0295 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 request for a team and trjExpensify June 17, 2026 12:07
@gijoe0295

gijoe0295 commented Jun 17, 2026

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 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-06-18.at.17.33.47.mov
Android: mWeb Chrome
Screen.Recording.2026-06-18.at.17.31.25.mov
iOS: HybridApp
Screen.Recording.2026-06-18.at.17.26.49.mov
iOS: mWeb Safari
Screen.Recording.2026-06-18.at.17.28.02.mov
MacOS: Chrome / Safari
Screen.Recording.2026-06-18.at.17.21.47.mov

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

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

if (isAdmin) {
// Admins open the details RHP directly instead of the room report, so the report is never fetched via ReportScreen.
// Fetch it here so the RHP has full data (participants, metadata) for Join, Invite and renaming.
openReport({reportID: report.reportID, introSelected, betas});

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2 Badge Fetch room data without marking the room read

When an admin who is already a member of a room opens it from Workspace settings → Rooms just to view details, this new openReport call uses the chat-opening path, whose implementation says it “updates the last read message” and sends useLastUnreadReportAction: true/clientLastReadTime. That means merely opening the details RHP can clear unread state for the room even though the user has not opened or read the conversation; use a report-data fetch that does not advance read state, or gate this to cases where marking read is intended.

Useful? React with 👍 / 👎.

@shubham1206agra shubham1206agra Jun 18, 2026

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.

@sumo-slonik This looks like a valid concern. Why have you marked this as 👎🏽 here?

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.

bump on this thread @sumo-slonik. Can we take off hold?

@sumo-slonik

Copy link
Copy Markdown
Contributor Author

@shubham1206agra Hi, I’m wondering whether you should have been automatically assigned to the review here instead of @gijoe0295, since it’s related to rooms.

@gijoe0295

Copy link
Copy Markdown
Contributor

Sorry but I'm already testing and filling the checklist 😿

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

LGTM

@melvin-bot
melvin-bot Bot requested a review from grgia June 18, 2026 10:35
@gijoe0295

Copy link
Copy Markdown
Contributor

Checklist is here

@shubham1206agra

Copy link
Copy Markdown
Contributor

Sorry @gijoe0295, but you won't be paid for this review as @sumo-slonik pointed out the wrong reviewer assignment before you filled any point in checklist. I will leave the decision to @grgia about this.

@grgia

grgia commented Jun 18, 2026

Copy link
Copy Markdown
Contributor

@gijoe0295 sorry about that. It's true that this is @shubham1206agra's issue

@grgia
grgia requested a review from shubham1206agra June 18, 2026 12:35
@shubham1206agra

Copy link
Copy Markdown
Contributor

@grgia @sumo-slonik Isn't this issue solvable from BE side? Am I missing something? This is same bug as incomplete report/participant object is being sent from BE.

@github-actions

Copy link
Copy Markdown
Contributor

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

@github-actions

This comment has been minimized.

@gijoe0295

Copy link
Copy Markdown
Contributor

@gijoe0295 sorry about that. It's true that this is @shubham1206agra's issue

Sure

@sumo-slonik

Copy link
Copy Markdown
Contributor Author

@grgia @sumo-slonik Isn't this issue solvable from BE side? Am I missing something? This is same bug as incomplete report/participant object is being sent from BE.

@shubcham, It doesn't seem like a backend issue to me. I fixed it purely on the frontend side, without any backend changes, and everything is working correctly now.

Could you please take a look and review the changes when you have a moment?

@shubham1206agra

Copy link
Copy Markdown
Contributor

@sumo-slonik Let's hold this PR on https://github.com/Expensify/Auth/pull/22368

@sumo-slonik sumo-slonik changed the title Load full report when admins open a room from the Workspace Rooms list [HOLD #22368] Load full report when admins open a room from the Workspace Rooms list Jun 23, 2026
@sumo-slonik

Copy link
Copy Markdown
Contributor Author

@sumo-slonik Let's hold this PR on https://github.com/Expensify/Auth/pull/22368

@shubham1206agra Unfortunately, I can't check the status of that PR. Do you have any updates on it?

@shubham1206agra

Copy link
Copy Markdown
Contributor

@sumo-slonik PR still in review

@sumo-slonik

Copy link
Copy Markdown
Contributor Author

@sumo-slonik PR still in review

thanks!

@grgia

grgia commented Jun 26, 2026

Copy link
Copy Markdown
Contributor

@sumo-slonik @shubham1206agra do we actually need to hold this PR on the auth fix or can they be separated?

@sumo-slonik

Copy link
Copy Markdown
Contributor Author

@sumo-slonik @shubham1206agra do we actually need to hold this PR on the auth fix or can they be separated?

I don’t think we need to block this PR on the auth fix. They look independent and shouldn’t conflict.

@shubham1206agra suggested we hold off, and then I assumed it is low priority, which is why I agreed to wait.

@shubham1206agra

Copy link
Copy Markdown
Contributor

https://github.com/Expensify/Auth/pull/22368 has been merged. Waiting for deploy. After this, retest the original issue.

Comment on lines +75 to +78
if (isAdmin) {
// Admins open the details RHP directly instead of the room report, so the report is never fetched via ReportScreen.
// Fetch it here so the RHP has full data (participants, metadata) for Join, Invite and renaming.
openReport({reportID: report.reportID, introSelected, betas});

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.

An admin who is a member of the room loses its unread indicator just by opening the details RHP from the rooms list, without ever reading the chat.

Add a flag to OpenReportActionParams (e.g. shouldMarkAsRead, default true) that skips useLastUnreadReportAction and clientLastReadTime when the caller only needs report data (note: this is a new openReport param).

Alternatively, can we retest the original issue given auth is deployed. And close this if it's been fixed?

@sumo-slonik

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

@grgia I retested #93248 on main with the auth fix deployed — Join is fixed now, but Invite and renaming the room from the RHP are still broken, so we still need this PR.

I also confirmed the unread concern (opening the RHP was clearing the unread indicator), so I added the shouldMarkAsRead param as you suggested — when false, OpenReport is sent without useLastUnreadReportAction and clientLastReadTime.

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.

@sumo-slonik Another auth PR in place to fix invite https://github.com/Expensify/Auth/pull/22816

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

If we're fixing this on the backend side as well, is it possible that editing the room from the RHP could be resolved the same way? In that case, this PR might not be necessary either.

What do you think, @shubham1206agra @grgia?

@sumo-slonik sumo-slonik changed the title [HOLD #22368] Load full report when admins open a room from the Workspace Rooms list Load full report when admins open a room from the Workspace Rooms list Jul 13, 2026
@github-actions

Copy link
Copy Markdown
Contributor

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

@github-actions

This comment has been minimized.

@sumo-slonik

Copy link
Copy Markdown
Contributor Author

I’ll be away for the rest of the week, so I’m leaving this PR in @WojtekBoman good hands.

@grgia
grgia merged commit f06a939 into Expensify:main Jul 16, 2026
38 checks passed
@OSBotify

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

Copy link
Copy Markdown
Contributor

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

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to staging by https://github.com/grgia in version: 9.4.36-0 🚀

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

@MelvinBot

Copy link
Copy Markdown
Contributor

🤖 No help site changes required.

This PR is a data-loading bug fix — when an admin opens a room from the Workspace Rooms list, the full report is now fetched before navigating so Join, Invite member, and room renaming operate on complete data. It doesn't add, remove, or change any user-facing feature, workflow, copy, or button label.

The relevant help article — Find Rooms in a Workspace — already documents the correct, intended behavior this fix restores:

"Selecting a room opens its details page. Workspace members can click Go to room to open the conversation. Workspace admins can view the room details page and manage room settings and membership."
"Opening a room from the Rooms directory does not automatically join you to the room."

Since the documented behavior is unchanged and the PR simply makes the product match it, no draft PR was created.

@sumo-slonik, let me know if you'd still like a docs update anyway and I can draft one.

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.

6 participants