I've used json {"active": "false"} or {"active": false} to PUT a value. It responds: "error.no.value.found.to.be.changed" while GET gives the current {"active": true}.
According to the documentation, PUT requests against the User entity are in "experimental" mode, and it does not even appear to support that particular field. From the documentation...
https://docs.atlassian.com/jira/REST/6.2.4/#d2e4551
Modify user. The "value" fields present will override the existing value. Fields skipped in request will not be changed.
<h6><h6>Example</h6>
{ "name": "eddie", "emailAddress": "eddie@atlassian.com", "displayName": "Eddie of Atlassian" }
Thank you, Geoffrey. I suspected it but wanted a confirmation that everything is correct from my side.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.