-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[$250] Chat - Self DM is automatically pinned and doesn't disappear in #focus mode #42070
Comments
Triggered auto assignment to @laurenreidexpensify ( |
@laurenreidexpensify 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 |
We think that this bug might be related to #wave-collect - Release 1 |
Job added to Upwork: https://www.upwork.com/jobs/~01f93577661d3c2dad |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @ishpaul777 ( |
should the self DM be unpinned? |
NAB, this looks like expected behaviour |
@trjExpensify can you confirm? |
Yeah, the selfDM is intentionally pinned to the LHN upon account creation. Pinned chats show in the #focus mode LHN. |
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.73-0
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Issue reported by: Applause - Internal Team
Issue found when executing PR #40336
Action Performed:
Expected Result:
The self DM is not displayed
Actual Result:
The self DM is automatically pinned, and is displayed in focus mode in LHN
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
Bug6479249_1715599999583.40336.mp4
View all open jobs on GitHub
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @ishpaul777The text was updated successfully, but these errors were encountered: