Skip to content
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

[FIX] Fix user's customFields not being saved correctly #7358

Merged
merged 1 commit into from
Jun 28, 2017

Conversation

sampaiodiego
Copy link
Member

@sampaiodiego sampaiodiego commented Jun 28, 2017

@RocketChat/core

@sampaiodiego sampaiodiego added this to the 0.57.0 milestone Jun 28, 2017
@engelgabriel engelgabriel temporarily deployed to rocket-chat-pr-7358 June 28, 2017 12:55 Inactive
@rodrigok rodrigok merged commit 9547687 into release-candidate Jun 28, 2017
@rodrigok rodrigok deleted the fix-users-customfields branch June 28, 2017 14:31
@waveyuk
Copy link

waveyuk commented Jun 28, 2017

Apologies if this is the wrong place to post this...
Will this fix allow custom fields added to appear on a user's profile when viewed in the right-hand pane in either public chat channels, private groups and direct messages? This is something that has limited the software so far as ideally I would like people to be able to have a Status field that they could fill out, for example "Away until 1st July". I have raised this as an issue previously.
Thanks

@sampaiodiego
Copy link
Member Author

hi @waveyuk .. this will not show custom fields on right pane.. this is just to fix saving custom fields by the REST API.

@waveyuk
Copy link

waveyuk commented Jun 29, 2017

Hi @sampaiodiego
Thanks for clarifying this. I hope that in the next release you can find a way to allow these custom fields to be shown on the profile as it's quite a game changer for me not to be able to add them, or as I say, a status message field that users can update.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants