Skip to content

[hold for payment 2025-05-22] [$250] Thread-User invited via Whisper not shown in Members section & cannot invited in 2nd expense #61474

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
3 of 8 tasks
jponikarchuk opened this issue May 6, 2025 · 16 comments
Assignees
Labels
Awaiting Payment Auto-added when associated PR is deployed to production Bug Something is broken. Auto assigns a BugZero manager. External Added to denote the issue can be worked on by a contributor Reviewing Has a PR in review Weekly KSv2

Comments

@jponikarchuk
Copy link

jponikarchuk commented May 6, 2025

If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!


Version Number: V9.1.40-0
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from TestRail: N/a
Email or phone of affected tester (no customers): Slottwo1 [email protected]
Issue reported by: Applause Internal Team
Device used: Redminote note 10s android 13
App Component: Chat Report View

Action Performed:

  1. Go to https://staging.new.expensify.com/home
  2. Open workspace chat
  3. Create a manual expense
  4. Open the expense
  5. Send a mention
  6. Tap invite
  7. Check in members page, invited member is not added by tapping header - members section
  8. Create another expense
  9. Open the expense
  10. Invite the same user via whisper
  11. Note mention is not shown
  12. Send another mention
  13. Invite them by tapping invite in whisper
  14. Go to members and check invited member is displayed
  15. Open first expense and note user invited not shown in members section

Expected Result:

User invited to a report via Whisper must be shown in Members section of that report.

Actual Result:

User invited via whisper to a report is not always shown in the members section of that report.

Workaround:

Unknown

Platforms:

  • Android: App
  • Android: mWeb Chrome
  • iOS: App
  • iOS: mWeb Safari
  • iOS: mWeb Chrome
  • Windows: Chrome
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Screenshots/Videos

1.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~021920119943181329486
  • Upwork Job ID: 1920119943181329486
  • Last Price Increase: 2025-05-07
Issue OwnerCurrent Issue Owner: @VictoriaExpensify
@jponikarchuk jponikarchuk added Daily KSv2 Bug Something is broken. Auto assigns a BugZero manager. labels May 6, 2025
Copy link

melvin-bot bot commented May 6, 2025

Triggered auto assignment to @joekaufmanexpensify (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

@joekaufmanexpensify
Copy link
Contributor

Hmm, interesting. I am checking to make sure it is expected that the parent report and each child transaction thread can have separate member lists. I think they can. If so, I agree you should be able to invite a user via mention to the parent report or any of its child transaction threads and actually have them be added to the thread.

@bernhardoj
Copy link
Contributor

Proposal

Please re-state the problem that we are trying to solve in this issue.

User invited from whisper isn't shown on the members page.

What is the root cause of that problem?

The user is actually invited successfully, and the expense report contains the member from expense A and expense B. For example, if we invite user 1 in expense A and user 2 in expense B, the expense report will have both user 1 and 2as the members.

The problem here is that those users have a hidden notification preference, and we exclude it from the members.

const participants = useMemo(() => {
return getParticipantsList(report, personalDetails, shouldOpenRoomMembersPage);
}, [report, personalDetails, shouldOpenRoomMembersPage]);

App/src/libs/ReportUtils.ts

Lines 2769 to 2770 in 1082941

const shouldExcludeHiddenParticipants = !isReportGroupChat && !isReportIOU;
const chatParticipants = getParticipantsAccountIDsForDisplay(report, isRoomMembersList || shouldExcludeHiddenParticipants, false, false, reportMetadata);

What changes do you think we should make in order to solve the problem?

If we want to include hidden notification preference users in the members of both expense report and transaction thread, then we can update shouldExcludeHiddenParticipants to also check for expense report and transaction thread (isMoneyRequest, isMoneyRequestReport, and track too if needed).

What specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?

Create a test for getParticipantsList and make sure all hidden participant is returned for expense and transaction thread.

@joekaufmanexpensify
Copy link
Contributor

Looked into this more, and if someone is invited via a mention to a specific report, we do want to add them to that specific report and show them on the members list.

@joekaufmanexpensify joekaufmanexpensify added the External Added to denote the issue can be worked on by a contributor label May 7, 2025
@melvin-bot melvin-bot bot changed the title Thread-User invited via Whisper not shown in Members section & cannot invited in 2nd expense [$250] Thread-User invited via Whisper not shown in Members section & cannot invited in 2nd expense May 7, 2025
Copy link

melvin-bot bot commented May 7, 2025

Job added to Upwork: https://www.upwork.com/jobs/~021920119943181329486

@melvin-bot melvin-bot bot added the Help Wanted Apply this label when an issue is open to proposals by contributors label May 7, 2025
Copy link

melvin-bot bot commented May 7, 2025

Triggered auto assignment to Contributor-plus team member for initial proposal review - @ishpaul777 (External)

@bradyrose
Copy link

bradyrose commented May 8, 2025

Withdrawing this proposal to comply with Expensify’s one-proposal-at-a-time policy.
Hope to circle back if it’s still open later. Thanks!

Copy link
Contributor

github-actions bot commented May 8, 2025

⚠️ Thanks for your proposal. Please update it to follow the proposal template, as proposals are only reviewed if they follow that format (note the mandatory sections).

@bradyrose
Copy link

⚠️ Thanks for your proposal. Please update it to follow the proposal template, as proposals are only reviewed if they follow that format (note the mandatory sections).

thanks, I have updated the proposal.

@ishpaul777
Copy link
Contributor

@bernhardoj proposal makes sense to me 🚀

🎀 👀 🎀

Copy link

melvin-bot bot commented May 9, 2025

Triggered auto assignment to @carlosmiceli, see https://stackoverflow.com/c/expensify/questions/7972 for more details.

@melvin-bot melvin-bot bot removed the Help Wanted Apply this label when an issue is open to proposals by contributors label May 9, 2025
@melvin-bot melvin-bot bot added Reviewing Has a PR in review Weekly KSv2 and removed Daily KSv2 labels May 10, 2025
@bernhardoj
Copy link
Contributor

PR is ready

cc: @ishpaul777

@joekaufmanexpensify
Copy link
Contributor

PR in review

@joekaufmanexpensify
Copy link
Contributor

Automation failed here. Payment is due 2025-05-22.

@joekaufmanexpensify joekaufmanexpensify changed the title [$250] Thread-User invited via Whisper not shown in Members section & cannot invited in 2nd expense [hold for payment 2025-05-22] [$250] Thread-User invited via Whisper not shown in Members section & cannot invited in 2nd expense May 19, 2025
@joekaufmanexpensify joekaufmanexpensify added the Awaiting Payment Auto-added when associated PR is deployed to production label May 19, 2025
@joekaufmanexpensify joekaufmanexpensify removed their assignment May 20, 2025
@joekaufmanexpensify joekaufmanexpensify added Bug Something is broken. Auto assigns a BugZero manager. and removed Bug Something is broken. Auto assigns a BugZero manager. labels May 20, 2025
Copy link

melvin-bot bot commented May 20, 2025

Triggered auto assignment to @VictoriaExpensify (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

@melvin-bot melvin-bot bot added Daily KSv2 and removed Weekly KSv2 labels May 20, 2025
@joekaufmanexpensify joekaufmanexpensify added Weekly KSv2 and removed Daily KSv2 labels May 20, 2025
@joekaufmanexpensify
Copy link
Contributor

Assigning another BZ because I am OOO from May 21st - May 30th. If it's still open then I'll take it back over! Next steps are to issue payment on 2025-05-22. Payment is:

@joekaufmanexpensify joekaufmanexpensify self-assigned this May 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Awaiting Payment Auto-added when associated PR is deployed to production Bug Something is broken. Auto assigns a BugZero manager. External Added to denote the issue can be worked on by a contributor Reviewing Has a PR in review Weekly KSv2
Projects
Status: No status
Development

No branches or pull requests

7 participants