Conversation
E2E tests not automatically triggered, because PR has no approval yet. Please ask a developer to review and then try again to attach the QA label. |
@matthewbirtch / @BenCookie95 / @kostaspt - I saw they mentioned no ETA on fixing this for forks so I just moved it over here. Same PR as #12147. Just to unblock it. I'll merge the cloud server fix in just a moment |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@coltoneshaw custom status shows correctly, except in a few places.
Custom Status is not getting shown in the thread
Custom Status is not getting shown in Saved Posts
Custom Status is not getting shown in Recent mentions
Unable to type in the Search emojis
field
UserA
is not able to see the custom status of UserB
in the channel and DM
@furqanmlk - the unable to type thing is a bug that was reported and fixed https://mattermost.atlassian.net/browse/MM-5079 The other three (mentions, DM sidebar, and threads) seem to work in community just fine. Let me see if updating this PR fixes it |
@furqanmlk - I updated the branch and just retried everything. It's all resolved that you listed. Let me know if you see anything else! Saved PostsDM (note sys admin doesn't have a status set)Recent Mentions |
/e2e-test |
Successfully triggered E2E testing! |
Test server destroyed |
1 similar comment
Test server destroyed |
Duplicate of #12147 to fix the s3 bucket issue on forks.
Summary
Added the custom user status in the RHS user list, fixed the style in the team members list, and added it to the Sys Console > Users list for fun.
Ticket Link
https://mattermost.atlassian.net/browse/MM-50308
Screenshots
Release Note