You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Paid] [$500] Chat - Unread message green line marker remains after opening the new message #31623
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:
Navigate to staging.new.expensify.com.
[User A] Create a group chat with User B and User C.
[User B] Open the group chat.
[User B] Navigate to a different chat.
[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?
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
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:
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
Activity
[-]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[/+]melvin-bot commentedon Nov 21, 2023
Job added to Upwork: https://www.upwork.com/jobs/~01a6c492f2a1b3468a
melvin-bot commentedon Nov 21, 2023
Triggered auto assignment to @anmurali (
Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.melvin-bot commentedon Nov 21, 2023
Bug0 Triage Checklist (Main S/O)
Platformsin OP are ✅)melvin-bot commentedon Nov 21, 2023
Triggered auto assignment to Contributor-plus team member for initial proposal review - @cubuspl42 (
External)43 remaining items
melvin-bot commentedon Nov 23, 2023
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:
luacmartins commentedon Dec 4, 2023
I think we're only missing the BZ checklist and payment here
jakub-trzebiatowski commentedon Dec 4, 2023
No payment for me, I wasn't involved in practice in this one. Should I still fill the checklist?
anmurali commentedon Dec 7, 2023
I paid @tienifr and it doesn't look like there is an external issue reporter.
[-][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[/+]melvin-bot commentedon Dec 8, 2023
@nkuoch, @cubuspl42, @anmurali, @luacmartins, @tienifr Whoops! This issue is 2 days overdue. Let's get this updated quick!
luacmartins commentedon Dec 8, 2023
It seems like all payments have been issued. I think we're good to close this one! Thanks everyone!