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
Users custom status drops on change presence status #25940
Comments
5.3.5 still have that issue |
@hardikbhatia777 is this something you might want to be assigned? |
Hey @casalsgh I would like to work on this issue. Found useStatusText, but not sure if it's the file containing the issue. Is there a way to check if the user has set up a custom status cause the function |
Sorry, I did not get a notification for this post. I'll look into it and get back to you :) |
@casalsgh this feature was implemented like that by design, its ok if we decide/want to change it, but not a bug. and the changes and descriptions should reflect this decision |
FYI to all here -> Gazzo had the latest and feature is working as designed. Per our Product squad we are looking to change behaviour in the future as follows: If anyone is in to perform behavior change that would be great (will assign) |
@casalsgh I'll be happy to work on this :) Just for some clarity on the idea, you want there to be a menu which lists out previously saved custom statuses and a text box for anything new, like this? |
There is no need to create a dropdown menu. Just bringing the text box with the previously used text is enough. |
@hardikbhatia777 Just complementing, I don't think we have the need to save this info anywhere permanent, you could save it directly to the localstorage and then just fill the box with whatever was there before |
@ankar84 behaviour changes implemented with PR-31237 by @hardikbhatia777 . Will be on 6.6.0 release and with that considering this item closed. Please mention me here if you have any other comments |
Description:
Users custom status drops on change presence status
Steps to reproduce:
Expected behavior:
Custom status should remain despite of presence status.
I'm not 100% sure, but on a pre 4.8 versions that was true.
Actual behavior:
Server Setup Information:
Client Setup Information
Additional context
I guess that on a previous versions Custom status remain despite presence status changes
Relevant logs:
The text was updated successfully, but these errors were encountered: