Skip to content

[HOLD for payment 2024-03-14] [HOLD for payment 2024-03-13] Group chat - Join button appears in header after creating a group chat #37709

Closed

Description

@m-natarajan

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!


Version Number: 1.4.47-0
Reproducible in staging?: y
Reproducible in production?: n
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause internal team
Slack conversation:

Action Performed:

  1. Go to staging.new.expensify.com
  2. Go to FAB > Start chat.
  3. Create a group chat.

Expected Result:

Join button will not appear in group chat.

Actual Result:

Join button shows up in group chat header.
The same issue also occurs when User B opens task report created by User A.

Workaround:

unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

  • Android: Native
  • Android: mWeb Chrome
  • iOS: Native
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence

Bug6402233_1709602487588.bandicam_2024-03-05_05-49-40-438__1_.mp4

View all open jobs on GitHub

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    on Mar 5, 2024
  2. melvin-bot commented on Mar 5, 2024

    @melvin-bot

    Triggered auto assignment to @JmillsExpensify (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

  3. github-actions commented on Mar 5, 2024

    @github-actions
    Contributor

    👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

    1. Identify the pull request that introduced this issue and revert it.
    2. Find someone who can quickly fix the issue.
    3. Fix the issue yourself.
  4. melvin-bot commented on Mar 5, 2024

    @melvin-bot

    Triggered auto assignment to @MonilBhavsar (Engineering), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

  5. m-natarajan commented on Mar 5, 2024

    @m-natarajan
    Author

    We think that this bug might be related to #vip-vsb
    cc @quinthar

  6. m-natarajan commented on Mar 5, 2024

    @m-natarajan
    Author

    @MonilBhavsar FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors.

  7. nkdengineer commented on Mar 5, 2024

    @nkdengineer
    Contributor

    Proposal

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

    • Group chat - Join button appears in header after creating a group chat

    What is the root cause of that problem?

    • Regression from Track expense/self dm #37165
    • We are using const canJoinOrLeave = isChatThread || !isSelfDM || isUserCreatedPolicyRoom || canLeaveRoom in here to display the join button

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

    • Should use const canJoinOrLeave = (isChatThread || isUserCreatedPolicyRoom || canLeaveRoom) && !isSelfDM instead

    What alternative solutions did you explore? (Optional)

    • Or we just need to remove !isSelfDM
  8. ShridharGoel commented on Mar 5, 2024

    @ShridharGoel
    Contributor

    Proposal

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

    Join button appears in header after creating a group chat.

    What is the root cause of that problem?

    There is a check !isSelfDM in canJoinOrLeave but no way to check if user is already a participant.

    const canJoinOrLeave = isChatThread || !isSelfDM || isUserCreatedPolicyRoom || canLeaveRoom;
    

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

    A check needs to be added for ensuring that user is not already a participant while creating canJoin.
    !ReportUtils.isReportParticipant(currentUserAccountID ?? 0, props.report)

    const canJoin = canJoinOrLeave && !isWhisperAction && props.report.notificationPreference === CONST.REPORT.NOTIFICATION_PREFERENCE.HIDDEN && !ReportUtils.isReportParticipant(currentUserAccountID ?? 0, props.report);
    
  9. 11 remaining items

  10. changed the title [-]Group chat - Join button appears in header after creating a group chat[/-] [+][HOLD for payment 2024-03-13] Group chat - Join button appears in header after creating a group chat[/+] on Mar 6, 2024
  11. melvin-bot commented on Mar 6, 2024

    @melvin-bot

    Reviewing label has been removed, please complete the "BugZero Checklist".

  12. melvin-bot commented on Mar 6, 2024

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.47-10 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

    If no regressions arise, payment will be issued on 2024-03-13. 🎊

    For reference, here are some details about the assignees on this issue:

    • @paultsimura requires payment (Needs manual offer from BZ)
    • @ishpaul777 requires payment (Needs manual offer from BZ)
  13. melvin-bot commented on Mar 6, 2024

    @melvin-bot

    BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:

    • [@paultsimura / @ishpaul777] The PR that introduced the bug has been identified. Link to the PR:
    • [@paultsimura / @ishpaul777] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment:
    • [@paultsimura / @ishpaul777] A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion:
    • [@paultsimura / @ishpaul777] Determine if we should create a regression test for this bug.
    • [@paultsimura / @ishpaul777] If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again.
    • [@JmillsExpensify] Link the GH issue for creating/updating the regression test once above steps have been agreed upon:
  14. paultsimura commented on Mar 6, 2024

    @paultsimura
    Contributor

    The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.47-10 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

    If no regressions arise, payment will be issued on 2024-03-13. 🎊

    For reference, here are some details about the assignees on this issue:

    • @paultsimura requires payment (Needs manual offer from BZ)
    • @ishpaul777 requires payment (Needs manual offer from BZ)

    No payment here – it was fixed as a regression.

  15. MonilBhavsar commented on Mar 7, 2024

    @MonilBhavsar
    Contributor

    No payment required. So closing this. Thanks all!

  16. changed the title [-][HOLD for payment 2024-03-13] Group chat - Join button appears in header after creating a group chat[/-] [+][HOLD for payment 2024-03-14] [HOLD for payment 2024-03-13] Group chat - Join button appears in header after creating a group chat[/+] on Mar 7, 2024
  17. melvin-bot commented on Mar 7, 2024

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.48-0 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

    If no regressions arise, payment will be issued on 2024-03-14. 🎊

    For reference, here are some details about the assignees on this issue:

    • @paultsimura requires payment (Needs manual offer from BZ)
    • @ishpaul777 requires payment (Needs manual offer from BZ)
  18. melvin-bot commented on Mar 7, 2024

    @melvin-bot

    BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:

    • [@paultsimura / @ishpaul777] The PR that introduced the bug has been identified. Link to the PR:
    • [@paultsimura / @ishpaul777] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment:
    • [@paultsimura / @ishpaul777] A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion:
    • [@paultsimura / @ishpaul777] Determine if we should create a regression test for this bug.
    • [@paultsimura / @ishpaul777] If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again.
    • [@JmillsExpensify] Link the GH issue for creating/updating the regression test once above steps have been agreed upon:
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionBugSomething is broken. Auto assigns a BugZero manager.EngineeringWeeklyKSv2

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions