Skip to content

[Paid] [$500] Chat - Unread message green line marker remains after opening the new message #31623

Closed

Description

@izarutskaya

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: v1.4.1-7
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. Navigate to staging.new.expensify.com.
  2. [User A] Create a group chat with User B and User C.
  3. [User B] Open the group chat.
  4. [User B] Navigate to a different chat.
  5. [User B] Return to the group chat.

Expected Result:

The unread message green line marker will disappear.

Actual Result:

The unread message green line marker remains.

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

Bug6285403_1700568404354.20231121_125703.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~01a6c492f2a1b3468a
  • Upwork Job ID: 1726945329577918464
  • Last Price Increase: 2023-11-21
  • Automatic offers:
    • cubuspl42 | Reviewer | 27770767
    • tienifr | Contributor | 27770769
Issue OwnerCurrent Issue Owner: @cubuspl42

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    ExternalAdded to denote the issue can be worked on by a contributor
    BugSomething is broken. Auto assigns a BugZero manager.
    on Nov 21, 2023
  2. changed the title [-]Chat - Unread message green line marker remains after opening the new message[/-] [+][$500] Chat - Unread message green line marker remains after opening the new message[/+] on Nov 21, 2023
  3. melvin-bot commented on Nov 21, 2023

    @melvin-bot
  4. melvin-bot commented on Nov 21, 2023

    @melvin-bot

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

  5. added
    Help WantedApply this label when an issue is open to proposals by contributors
    on Nov 21, 2023
  6. melvin-bot commented on Nov 21, 2023

    @melvin-bot

    Bug0 Triage Checklist (Main S/O)

    • This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
    • This bug is not a duplicate report (check E/App issues and #expensify-bugs)
      • If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead
    • This bug is reproducible using the reproduction steps in the OP. S/O
      • If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
      • If the reproduction steps aren't clear and you determine the correct steps, please update the OP.
    • This issue is filled out as thoroughly and clearly as possible
      • Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.
    • I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync
  7. melvin-bot commented on Nov 21, 2023

    @melvin-bot

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

  8. 43 remaining items

  9. melvin-bot commented on Nov 23, 2023

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

    • [@cubuspl42] The PR that introduced the bug has been identified. Link to the PR:
    • [@cubuspl42] 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:
    • [@cubuspl42] 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:
    • [@cubuspl42] Determine if we should create a regression test for this bug.
    • [@cubuspl42] 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.
    • [@anmurali] Link the GH issue for creating/updating the regression test once above steps have been agreed upon:
  10. luacmartins commented on Dec 4, 2023

    @luacmartins
    Contributor

    I think we're only missing the BZ checklist and payment here

  11. jakub-trzebiatowski commented on Dec 4, 2023

    @jakub-trzebiatowski
    Contributor

    No payment for me, I wasn't involved in practice in this one. Should I still fill the checklist?

  12. anmurali commented on Dec 7, 2023

    @anmurali

    I paid @tienifr and it doesn't look like there is an external issue reporter.

  13. removed
    Awaiting PaymentAuto-added when associated PR is deployed to production
    on Dec 7, 2023
  14. changed the title [-][HOLD for payment 2023-11-30] [$500] Chat - Unread message green line marker remains after opening the new message[/-] [+][Paid] [$500] Chat - Unread message green line marker remains after opening the new message[/+] on Dec 7, 2023
  15. melvin-bot commented on Dec 8, 2023

    @melvin-bot

    @nkuoch, @cubuspl42, @anmurali, @luacmartins, @tienifr Whoops! This issue is 2 days overdue. Let's get this updated quick!

  16. luacmartins commented on Dec 8, 2023

    @luacmartins
    Contributor

    It seems like all payments have been issued. I think we're good to close this one! Thanks everyone!

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

Metadata

Metadata

Labels

BugSomething is broken. Auto assigns a BugZero manager.DailyKSv2EngineeringExternalAdded to denote the issue can be worked on by a contributor

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions