Project

General

Profile

Actions

Defect #10583

open

JSON property key for assignee is not unique in REST_API

Added by Matthias Paul Scholz almost 12 years ago. Updated about 7 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
REST API
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Resolution:
Affected version:

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.

Actions

Also available in: Atom PDF