-
Notifications
You must be signed in to change notification settings - Fork 162
-
Notifications
You must be signed in to change notification settings - Fork 162
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
allow to unset assigned_to_id of issues #306
Comments
@akohlbecker thank you for reporting this. I do not actively work on this project anymore. if you can submit a PR with a fix that would be in line with the current architecture, I can review & merge. |
closing since no one volunteered to work on this issue. |
We have found today the same problem when I migrated from Redmine v3.1.2 (unset assignee_to_id from Redmine Java API worked fine) to v3.4.11 (assigned_to_id can't be unset by API). Our workaround has been to change the addIfSet method in the RedmineJSONBuilder class of the Redmine Java API. I share it for if this may help someone
|
This seems to work now on Redmine |
The
assigned_to_id
of an existing issue can not be unset:will cause the Transport to send a
null
value to the REST API:but Redmine (v.3.3.6) ignores this. The only value which causes the issue service to reset the
assigned_to_id
is an empty string:The text was updated successfully, but these errors were encountered: