Defect #10583
JSON property key for assignee is not unique in REST_API
| Status: | New | Start date: | ||
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 0% | |
| Category: | - | |||
| Target version: | - | |||
| Affected version: | 1.3.1 | Resolution: |
Description
When using the JSON-based version of the Redmine REST API for CRUD operations of issues, the JSON key for the assignee of the issue is not unique:
for creation, one needs to use "assigned_to_id"; when retrieving issues, though, the assignee's id is transmitted using the key "assigned_to".
In java-based clients (for instance the Redmine Java API), this makes usage of Gson for parsing and creating JSON code that is accepted by Redmine pretty hard, as Gson uses a (single) annotation on the members for specifying that kind of serialization information.