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
Version Number: v9.1.45-3 Reproducible in staging?: Yes Reproducible in production?: No If this was caught during regression testing, add the test name, ID and link from TestRail:#61376 Email or phone of affected tester (no customers):[email protected] Issue reported by: Applause Internal Team Device used: Samsung Galaxy A02s/12 App Component: Left Hand Navigation (LHN)
Action Performed:
Open any chat> Submit scan request that will fall
When scan request fail delete the request
Go to LHN and take a look of present chats
Expected Result:
There should be no Hidden chat and red dot on that chat
Actual Result:
Hidden chat with red dot displayed on LHN when delete failed scan request
👋 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:
Identify the pull request that introduced this issue and revert it.
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.45-3
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from TestRail: #61376
Email or phone of affected tester (no customers): [email protected]
Issue reported by: Applause Internal Team
Device used: Samsung Galaxy A02s/12
App Component: Left Hand Navigation (LHN)
Action Performed:
Expected Result:
There should be no Hidden chat and red dot on that chat
Actual Result:
Hidden chat with red dot displayed on LHN when delete failed scan request
Workaround:
Unknown
Platforms:
Screenshots/Videos
Bug6830283_1747174277669.Recording__5471.mp4
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: