Skip to content

Group chat - Selected user is highlighted after clicking Add to group #51786

Closed

Description

@lanitochka17

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: 9.0.56-0
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: N/A
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): applausetester+kh2310001@applause.expensifail.com
Issue reported by: Applause - Internal Team

Action Performed:

  1. Go to staging.new.expensify.com
  2. Go to FAB > Start chat
  3. Click Add to group next to user
  4. Click Next

Expected Result:

The selected user will not be highlighted (production behavior)

Actual Result:

The selected user is highlighted

Workaround:

Unknown

Platforms:

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

  • Android: Standalone
  • Android: HybridApp
  • Android: mWeb Chrome
  • iOS: Standalone
  • iOS: HybridApp
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence
Bug6651135_1730378824735.20241031_204614.mp4

View all open jobs on GitHub

Activity

  1. melvin-bot commented on Oct 31, 2024

    @melvin-bot

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

  2. melvin-bot commented on Oct 31, 2024

    @melvin-bot

    💬 A slack conversation has been started in #expensify-open-source

  3. github-actions commented on Oct 31, 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. mjasikowski commented on Oct 31, 2024

    @mjasikowski
    Contributor

    Offending PR: #51158

  5. Beamanator commented on Nov 4, 2024

    @Beamanator
    Contributor

    Reverted in #51795 & that was checked off by applause, so seems to be fixed!

  6. mjasikowski commented on Nov 7, 2024

    @mjasikowski
    Contributor

    Fix was submitted in #51937

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions