-
Notifications
You must be signed in to change notification settings - Fork 10.1k
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
Cannot change "Post as" value for incoming webhook integration II #9477
Comments
Also have been seeing this for a while, since 0.58 ish... |
Can confirm same issue on version 0.58.4. (Running on linux x64 3.10.0-514.el7.x86_64 with Node v4.8.4) |
Can still confirm. RocketChat Version: 0.68.4 |
Still an issue with: The only error I could find was that one from the browser developer tools: |
Yep, can confirm, still an issue in 0.74.3 |
Still an issue on 1.1.1. Updated to 1.3.0 and the issue still persists. |
If you test on the latest as you should as per this: https://rocket.chat/docs/contributing/reporting-issues "Make sure you are running the latest version of Rocket.Chat. It’s very likely simply updating will resolve your issue." You will notice it still occurs on 1.3.0 |
Still there on 2.4.11 |
Still there on 3.1.1 |
Still there on 3.2.2 |
Still an issue in 3.4.2 |
Still there on 3.5.3 |
Still there on 3.7.1 |
Still an issue on 3.9.3 |
Still there on 3.13.2 |
Still here on 3.17.1 |
I have the issue still with 4.0.3 |
Still here on 4.4. |
Issue still present at 4.6.2 |
Still present in 5.3.6 |
Description:
Server Setup Information:
Steps to Reproduce:
Post as
Post as
and SaveExpected behavior:
The
Post as
should be changed to the new userActual behavior:
Post as
change does not persistPost as
does remain as the new value until reload.Relevant logs:
there is nothing in the logs at all relevant to editing the integration.
I tried different users, I tried restarting the server, I tried to change the user while the integration was disabled. All had no effect.
I'll look at the patch for #6869
The text was updated successfully, but these errors were encountered: